-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Want to adjust graceful shutdown time. #12831
Labels
domain: shutdown
Anything related to the shutdown of Vector
type: feature
A value-adding code addition that introduce new functionality.
Comments
Re-opening this to track making the shutdown configurable, separate from making it disablable (#9042). |
DominicBurkart
added a commit
that referenced
this issue
Jun 1, 2023
…able (#17479) We want to make the graceful shutdown period configurable instead of hardcoding it to sixty seconds. Issues: #9042 Remove 60s hard cutoff period for graceful shutdowns #12831 Want to adjust graceful shutdown time This is my first PR in vector, not sure if this is the correct approach: - are the ergonomics (-1 for no timeout, 0+ for timeout durations) good? - any test recommendations beyond manual testing? --------- Co-authored-by: Bruce Guenter <[email protected]>
Closed by #17479 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
domain: shutdown
Anything related to the shutdown of Vector
type: feature
A value-adding code addition that introduce new functionality.
A note for the community
The vector waits in-progress event's only for 1minutes. Please consider global options to adjust this time.
vector/src/topology/running.rs
Line 120 in ae94c8c
Use Cases
Adjust the shutdown wait time to prevent from data loss. Some situation (ex> es circuit breaking) the processing time is huge than normal situation. In that case, vector just loss all data when restart or stop the instance.
Attempted Solutions
No response
Proposal
No response
References
No response
Version
No response
The text was updated successfully, but these errors were encountered: