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

Make it easier to debug split brains and Raft-related Consul problems #1374

Closed
slackpad opened this issue Oct 30, 2015 · 9 comments
Closed
Labels
type/enhancement Proposed improvement or new feature

Comments

@slackpad
Copy link
Contributor

While interactively debugging an issue with @sean- a number of improvements were noted:

  1. It's hard to tell who a server is replicating TO, add IPs to the logs.
  2. It's hard to tell who the current leader is without logging into each and looking at consul info, make consul members show who the current leader is.
  3. Consider adding a 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.
  4. Add better metrics for Raft-related events such as leader elections. Right now we can only look at events which are output by all the nodes, so it's really hard to see the actual number of leadership transitions.
@highlyunavailable
Copy link
Contributor

#1378 already solves item 2 there, it just needs merging.

@trumant
Copy link
Contributor

trumant commented Dec 3, 2015

@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 consul info and consul members.

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.

@trumant
Copy link
Contributor

trumant commented Dec 3, 2015

@slackpad slackpad added the type/enhancement Proposed improvement or new feature label Jan 9, 2016
@slackpad slackpad self-assigned this Jan 9, 2016
@Dmitry1987
Copy link

Hi, I see it's an old topic, was it implemented?
how it's possible to contribute btw, and what are the chances for submitted code to be merged?

@slackpad
Copy link
Contributor Author

slackpad commented Mar 1, 2016

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.

@slackpad slackpad assigned sean- and unassigned slackpad Mar 1, 2016
@CpuID
Copy link

CpuID commented Jun 8, 2016

@slackpad or @sean- do either of you have any updates on this issue?

@CpuID
Copy link

CpuID commented Jun 8, 2016

It looks like 6cf21fb exposes the current raft peers list via consul info (item 3), which is a start.

@CpuID
Copy link

CpuID commented Jun 8, 2016

Confirmed #1849 being merged resolves item 2 - appears in consul info also.

@slackpad
Copy link
Contributor Author

slackpad commented May 2, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/enhancement Proposed improvement or new feature
Projects
None yet
Development

No branches or pull requests

6 participants