Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

shutdown_timeout does not take effect #2798

Closed
JuchangGit opened this issue Aug 22, 2024 · 1 comment
Closed

shutdown_timeout does not take effect #2798

JuchangGit opened this issue Aug 22, 2024 · 1 comment

Comments

@JuchangGit
Copy link

我的配置:

input:
  stdin:
    scanner:
      lines: {}
    auto_replay_nacks: true
buffer:
  none: {}
pipeline:
  threads: -1
  processors: []
output:
  stdout:
    codec: lines
  
shutdown_timeout: 5s

版本: redpanda-connect_4.30.1_windows_amd64

程序一直没有退出

@mihaitodor
Copy link
Collaborator

Hey @JuchangGit 👋 The shutdown_timeout field is only used to tell Connect how much time to keep retrying to send messages that are currently in-flight before giving up and shutting down as documented here. You still have to send it the SIGINT signal to trigger this shutdown or, alternatively, it will self-shutdown if all the inputs are finite (such as file) and they finish reading all the data they can read and this data is successfully written by the outputs. The shutdown_delay field allows you to specify an extra delay before it shuts down if, for example, you want to be able to have time to scrape metrics after the inputs shut down and all the messages have been written.

PS: Moving this to a discussion as per #2026.

@redpanda-data redpanda-data locked and limited conversation to collaborators Aug 22, 2024
@mihaitodor mihaitodor converted this issue into discussion #2800 Aug 22, 2024

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants