[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-3385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16856707#comment-16856707
 ] 

Hudson commented on ZOOKEEPER-3385:
-----------------------------------

SUCCESS: Integrated in Jenkins build Zookeeper-trunk-single-thread #390 (See 
[https://builds.apache.org/job/Zookeeper-trunk-single-thread/390/])
ZOOKEEPER-3385: fix build break. (nkalmar: rev 
5577d41da48feb8db3595d88a63096594c20fbb9)
* (edit) 
zookeeper-server/src/main/java/org/apache/zookeeper/server/admin/Commands.java


> Add admin command to display leader
> -----------------------------------
>
>                 Key: ZOOKEEPER-3385
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3385
>             Project: ZooKeeper
>          Issue Type: Improvement
>          Components: server
>    Affects Versions: 3.6.0
>            Reporter: Brian Nixon
>            Priority: Trivial
>              Labels: pull-request-available
>             Fix For: 3.6.0
>
>          Time Spent: 3h 10m
>  Remaining Estimate: 0h
>
> Each QuorumPeer prints the identity of the server it believes is the leader 
> in its logs but that is not easily turned into diagnostic information about 
> the state of the ensemble. It can be useful in debugging various issues, both 
> when a quorum is struggling to be established and when a minority of peers 
> are failing to follow, to see at a glance which peers are following the 
> leader elected by the majority and which peers are either not following or 
> following a different server.
> Create an admin command that exposes which server a peer believes is the 
> current leader.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to