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

Jump to bottom

Replicas did not reconnect #23

Closed
lguminski opened this issue Apr 28, 2016 · 2 comments
Closed

Replicas did not reconnect #23

lguminski opened this issue Apr 28, 2016 · 2 comments

Comments

@lguminski
Copy link

This could be a Consul issue, but I noticed that after leader re-election, there is "mysql-primary" service in Consul Web UI, but the following code (bin/triton-mysql.py)

nodes = consul.health.service(PRIMARY_KEY, passing=True)[1]

kept returning an empty set. This way replicas could not connect to master.
@lguminski lguminski changed the title Replicas not reconnect Replicas did not reconnect Apr 28, 2016
@tgross
Copy link
Contributor

tgross commented May 5, 2016

@lguminski do you have any logs for this? There's not really enough to go on and replicate this here.

@tgross
Copy link
Contributor

tgross commented Jun 6, 2016

Without logs I'm going to have to close this issue. Please open if you are able to get some more information for us.

@tgross tgross closed this as completed Jun 6, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@tgross @lguminski