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

0.4.6 Leader logging #913

Closed
WillPlatnick opened this issue Jul 31, 2014 · 2 comments · May be fixed by goraft/raft#229
Closed

0.4.6 Leader logging #913

WillPlatnick opened this issue Jul 31, 2014 · 2 comments · May be fixed by goraft/raft#229

Comments

@WillPlatnick
Copy link

Logging for leader changes does not appear to be correct on peers. I just setup a brand new, 3 node cluster.

From app02

[etcd] Jul 30 20:50:00.253 INFO      | app02: leader changed from '' to 'app03'.
[etcd] Jul 30 20:50:13.509 INFO      | app02: term #4 started.
[etcd] Jul 30 20:50:13.509 INFO      | app02: leader changed from 'app03' to ''.

But, if you curl leader information, it returns that there is a leader, app01. app01's logs agree.

[etcd] Jul 30 20:50:13.504 INFO      | app01: leader changed from 'app03' to ''.
[etcd] Jul 30 20:50:13.509 INFO      | app01: state changed from 'candidate' to 'leader'.
[etcd] Jul 30 20:50:13.509 INFO      | app01: leader changed from '' to 'app01'.
@yichengq
Copy link
Contributor

yichengq commented Aug 1, 2014

It seems that the peer doesn't printout the latest leader change.
We would add it to TODO list.

@xiang90
Copy link
Contributor

xiang90 commented Nov 30, 2014

@WillPlatnick This has been fix in the latest 0.5-alpha. Thanks for reporting!

@xiang90 xiang90 closed this as completed Nov 30, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging a pull request may close this issue.

3 participants