-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Handle SIGHUP event #1333
Comments
It is fixed in 0.9:
@jojohappy @bwplotka please close it. |
@daixiang0 Thanks! let me double check it ASAP. |
@daixiang0 Hi, maybe this issue is not fixed. @tomleb hopes that thanos should not exit when receive the SIGHUB. @tomleb As you said, thanos now use the flags as the provider for the most configurations, if you want to change them, restart it. On the other hand, it is a nice improvement to reload the configuration file of object store without restart. Maybe we can use the |
This issue/PR has been automatically marked as stale because it has not had recent activity. Please comment on status otherwise the issue will be closed in a week. Thank you for your contributions. |
Yea we might not handle it properly. I think it's a feature to reloader or just ignore SIGHUP. Help wanted (: |
Thanos, Prometheus and Golang version used
thanos: v0.5.0
What happened
Sending a SIGHUP signal to sidecar, store gateway, querier or compactor crashes it.
What you expected to happen
They should not crash. Maybe they should also reload configuration (?)
How to reproduce it (as minimally and precisely as possible):
I think thanos should at least not crash upon receiving a SIGHUP signal.
I understand that flags are used to configure thanos components, but it would be nice to have a way to reload configuration files immediately with a SIGHUP signal. This is what most applications do (eg: prometheus). Potential use case: Have an ansible handler sending the SIGHUP signal.
The text was updated successfully, but these errors were encountered: