Skip to content

[skip secret scan] Topology solution: Zookeeper requires leader restart #254

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

GeoffWilliams
Copy link
Contributor

MRC Zookeeper users will encounter ZOOKEEPER-2938 after recovering from a regional outage. The solution is a topology change.

Code:

  • Bind to 0.0.0.0
  • Only one Zookeeper per Zookeeper
  • Multiple Zookeepers to support more then one Zookeeper per region
  • Update CFK to 2.6.1 and CP to 7.4.1 to mitigate ZOOKEEPER-3988

Docs:

  • Correct description of Zookeeper topology (5 nodes, not 3)
  • Link to reference docs in troubleshooting section

Note: I have not tested these updated YAMLS in a lab

MRC Zookeeper users will encounter ZOOKEEPER-2938 after recovering from a regional outage. The solution is a topology change.

Code:

* Bind to `0.0.0.0`
* Only one Zookeeper per `Zookeeper`
* Multiple `Zookeepers` to support more then one Zookeeper per region
* Update CFK to 2.6.1 and CP to 7.4.1 to mitigate ZOOKEEPER-3988

Docs:
* Correct description of Zookeeper topology (5 nodes, not 3)
* Link to reference docs in troubleshooting section
@arodoni arodoni requested review from akhileshm1 and rohit2b July 28, 2023 18:16
@arodoni arodoni changed the title Topology solution: Zookeeper requires leader restart [skip secret scan] Topology solution: Zookeeper requires leader restart Jul 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant