Support for clustered (multi-server) setup #1
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
romming
approved these changes
Sep 18, 2019
|
Let's get back to this PR |
|
Can I merge this PR @romming ? |
|
Yeah, sounds good! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of the change
Note: upgrade ZooKeeper version to 3.4.14
This PR adds support for setting up a clustered ZooKeeper instance. In order to setup a ZooKeeper ensemble next env variables must be provided when running a container:
myid's file content).Additionally, a sample
docker-compose.yamlfile is included to setup a ensemble with 3 nodes.