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

Exhibitor instances can't see each other #3

Open
abhishekagarwal87 opened this issue Dec 5, 2016 · 2 comments
Open

Exhibitor instances can't see each other #3

abhishekagarwal87 opened this issue Dec 5, 2016 · 2 comments

Comments

@abhishekagarwal87
Copy link

Each exhibitor instance registers itself with hostname "unknown" in the shared configuration which means there is only one server registered. Due to this each zookeeper instance forms a separate quorum on its own, leading to all sorts of bugs and inconsistencies in application which depend on zookeeper.

Related issue: http://stackoverflow.com/questions/27087786/java-application-cannot-get-ip-address-of-the-host-in-docker-container-with-stat

@abhishekagarwal87
Copy link
Author

On aws, the workaround is to edit the command line once exhibitor is up and running and pass the exhibitor hostname like this

/exhibitor-wrapper -c zookeeper --headingtext "exhibitor-kafka" --zkconfigconnect master.mesos:2181 --zkconfigzpath "/exhibitor-dcosexhibitor-kafka" --hostname=`curl -fsSL http://169.254.169.254/latest/meta-data/local-ipv4` --hostname=`curl -fsSL http://169.254.169.254/latest/meta-data/local-ipv4`

@koboltmarky
Copy link

Hi,

i had the same problem you can use also use --hostname $LIBPROCESS_IP

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

No branches or pull requests

2 participants