-
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
downtime when upgrading single node overlord+coordinator to 0.13.0 #6854
Comments
I don't think that it's expected behavior. Do you have more than one overlord+coordinator (highly available deployment)? Or just 1? Did the system recover on its own? |
just 1. |
if KIS is being marked as stable (ref #6970) , this bug might be worth either fixing or atleast documenting. |
upgrading overlord nodes in 0.14.0 can result in few minutes of query downtime for KIS tasks, as noticed in apache#6854 this behavior should be documented until this is fixed by apache#6958 in 0.15.
This issue has been marked as stale due to 280 days of inactivity. It will be closed in 4 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. |
I noticed this behavior while upgrading from 0.12.3 to 0.13.0.
We have a single node merged overlord+coordinator.
The assumption is that since overlord/coordinator are not in the query path, upgrading that node shouldn't result in any downtime.
However, it seems when the node restarted (after upgrade), it terminated all existing KIS tasks and restarted them. This tooks a few minutes to happen, and during these 5 minutes or so, no realtime data was available for querying.
I saw a lot of messages like this during the node startup (after upgrade):
Is this expected behavior? If so, it might be worth documenting.
The text was updated successfully, but these errors were encountered: