-
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
kubernetes-druid-discovery-extension: stress-test overlord/coordinator leadership changes #11205
Conversation
…nt for BOOKMARK events
This pull request has been marked as stale due to 60 days of inactivity. It will be closed in 4 weeks if no further activity occurs. If you think that's incorrect or this pull request should instead be reviewed, please simply write any comment. Even if closed, you can still revive the PR at any time or discuss it on the dev@druid.apache.org list. Thank you for your contributions. |
This pull request/issue has been closed due to lack of activity. If you think that |
Fixes #10542
#10669 introduced the travis build that does data ingestion and querying on a zookeeper-less cluster using kubernetes druid extention. this patch adds another build that stress tests the leader election by repeatedly restarting coordinator/overlor and forcing leadership changes when kubernetes druid extension is used. this is a follow-up on #10680 .
In the process kubernetes java client dependency version is also updated to pull changes related to leader election improvements so that graceful coordinator/overlord shutdown immediately gives up leadership.
This PR has: