-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
Make it easier to debug split brains and Raft-related Consul problems #1374
Comments
#1378 already solves item 2 there, it just needs merging. |
@slackpad - I've been thinking that it would be great expose an HTTP agent endpoint at /v1/status/info and perhaps another at /v1/status/members that would provide the info currently emitted in difficult to parse format from I'd be happy to contribute a PR for this type of change if there is some agreement that it makes sense/would prove useful. |
Hi, I see it's an old topic, was it implemented? |
Hi all - this hasn't yet been implemented. I'd hold off on working on this for right now - @sean- is looking at a cluster-level status endpoint that would support this type of info. We should have more details in a bit. |
It looks like 6cf21fb exposes the current raft peers list via |
Confirmed #1849 being merged resolves item 2 - appears in |
This should be done now based on these features: |
While interactively debugging an issue with @sean- a number of improvements were noted:
consul info
, makeconsul members
show who the current leader is.consul peers
type command that shows the Raft details in a clear, parseable format. The peer set version is hard to understand, expose the Raft index.The text was updated successfully, but these errors were encountered: