[
https://issues.apache.org/jira/browse/ZOOKEEPER-1243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13134561#comment-13134561
]
Patrick Hunt commented on ZOOKEEPER-1243:
-----------------------------------------
Thomas also expressed issues with the way the 4lw code is structured. It's
certainly ripe for refactoring (hint hint ;-) ) esp given the duplication btw
NIO/Netty and taking into account the problems you've been finding. Regards.
> New 4lw for short simple monitoring ldck
> ----------------------------------------
>
> Key: ZOOKEEPER-1243
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1243
> Project: ZooKeeper
> Issue Type: Improvement
> Components: server
> Affects Versions: 3.3.3, 3.4.0
> Reporter: Camille Fournier
> Assignee: Camille Fournier
> Priority: Blocker
> Fix For: 3.3.4, 3.4.0
>
> Attachments: ZOOKEEPER-1243-2, ZOOKEEPER-1243-4.patch,
> ZOOKEEPER-1243.patch
>
>
> The existing monitoring fails so often due to
> https://issues.apache.org/jira/browse/ZOOKEEPER-1197 that we need a
> workaround. This introduces a short 4lw called ldck that just runs
> ServerStats.toString to get information about the sever's leadership status.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
