-
Notifications
You must be signed in to change notification settings - Fork 3.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
Nodes won't die if zookeeper went away. #2016
Comments
I believe this is the same issue as #660. |
I think you're right, although in my case it took ~40 minutes for nodes to go down after receiving SIGTERM. Anyway, any chances of this being resolved anytime soon? |
Absence of logging is probably because of #1387 not being in stable yet. |
This issue has been marked as stale due to 280 days of inactivity. It will be closed in 2 weeks if no further activity occurs. If this issue is still relevant, please simply write any comment. Even if closed, you can still revive the issue at any time or discuss it on the dev@druid.apache.org list. Thank you for your contributions. |
This issue has been closed due to lack of activity. If you think that is incorrect, or the issue requires additional review, you can revive the issue at any time. |
Scenario:
(Which is "fine", I guess.)
4. I do
kill -TERM <node_pid>
.5. Node says:
(Which seems to be normal, they always say that before dying.)
6. But... it does not die. Process is still displayed as running (in htop, etc.), no further logs or anything, though.
Using 0.8.2, happens for all kinds of nodes AFAICT.
Possibly worth noting that when I deliberately start a node when zookeeper is down, it exits fine on SIGTERM.
Probably wouldn't even notice it, but this confuses our systemd configs quite a bit :-/.
The text was updated successfully, but these errors were encountered: