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

Hypothesis: Disconnecting Leader and one Follower should not make cluster disruptive #45

Open
ChrisKujawa opened this issue Nov 17, 2020 · 1 comment
Labels
Contribution: Availability This issue will contribute to build up confidence in reliability. Contribution: Reliability This issue will contribute to build up confidence in reliability. Hypothesis A thing which worries us and is ready for exploration. Impact: High The issue has an high impact on the system. Likelihood: High The likelihood of this issue is really high!

Comments

@ChrisKujawa
Copy link
Member

Hypothesis

If we have disconnect a Leader with a follower, we expect that we still can create workflow instances and the leader keeps the leader. Follower will not start an election, since other follower is still connected.

@ChrisKujawa ChrisKujawa added Hypothesis A thing which worries us and is ready for exploration. Impact: High The issue has an high impact on the system. Likelihood: High The likelihood of this issue is really high! Contribution: Availability This issue will contribute to build up confidence in reliability. Contribution: Reliability This issue will contribute to build up confidence in reliability. labels Nov 17, 2020
@ChrisKujawa
Copy link
Member Author

Verified with https://github.com/zeebe-io/zeebe-chaos/blob/master/chaos-days/2021-01-07/README.md

Missing is an automated experiment

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Contribution: Availability This issue will contribute to build up confidence in reliability. Contribution: Reliability This issue will contribute to build up confidence in reliability. Hypothesis A thing which worries us and is ready for exploration. Impact: High The issue has an high impact on the system. Likelihood: High The likelihood of this issue is really high!
Projects
None yet
Development

No branches or pull requests

1 participant