[
https://issues.apache.org/jira/browse/ZOOKEEPER-1322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13165622#comment-13165622
]
Patrick Hunt commented on ZOOKEEPER-1322:
-----------------------------------------
I don't think it's this patch - given it passed once and failed the second
time.
quick look shows
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/817//testReport/org.apache.zookeeper.test/QuorumZxidSyncTest/testBehindLeader/
which is an intermittent failure I would think (can't agree who the leader is,
but I don't see anything related to this patch in there. Take a look at time
2011-12-08 21:03:40,921 and prior.
I'll trigger the patch test again.
It's fine to wait post 3.4.1, good idea.
> Cleanup/fix logging in Quorum code.
> -----------------------------------
>
> Key: ZOOKEEPER-1322
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1322
> Project: ZooKeeper
> Issue Type: Improvement
> Components: server
> Affects Versions: 3.4.0, 3.5.0
> Reporter: Patrick Hunt
> Assignee: Patrick Hunt
> Fix For: 3.5.0, 3.4.2
>
> Attachments: ZOOKEEPER-1322_br34.patch, ZOOKEEPER-1322_trunk.patch
>
>
> While triaging ZOOKEEPER-1319 I updated the code with the attached patch in
> order to help debug what was going on with that issue. I think it would be
> useful to include these changes in the project itself. ff to include in 3.4.1
> or push to 3.5.0.
> You should verify this with TRACE logging turned on in addition to INFO
> (default).
--
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
