Skip to content
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

Closed
wants to merge 32 commits into from

Conversation

himanshug
Copy link
Contributor

@himanshug himanshug commented May 5, 2021

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:

  • been self-reviewed.
  • added documentation for new or modified features or behaviors.
  • added Javadocs for most classes and all non-trivial methods. Linked related entities via Javadoc links.
  • added or updated version, license, or notice information in licenses.yaml
  • added comments explaining the "why" and the intent of the code wherever would not be obvious for an unfamiliar reader.
  • added unit tests or modified existing tests to cover new code paths, ensuring the threshold for code coverage is met.
  • added integration tests.
  • been tested in a test Druid cluster.

@stale
Copy link

stale bot commented Apr 27, 2022

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.

Copy link

github-actions bot commented Nov 4, 2023

This pull request/issue has been closed due to lack of activity. If you think that
is incorrect, or the pull request requires review, you can revive the PR at any time.

@github-actions github-actions bot closed this Nov 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Create a travis build that runs Druid on a K8S Cluster and runs the integration tests
2 participants