[
https://issues.apache.org/jira/browse/ZOOKEEPER-62?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stu Hood updated ZOOKEEPER-62:
------------------------------
Attachment: zoo-log.tgz
Here is an example of the problem from r701369. In this 3 peer ZooKeeper setup,
one peer grabbed leadership to start, and then lost it, going into an infinite
loop, while the other peers went about their business.
But by far the most common log messages that are repeated are the ones
referring to opening and closing transaction logs, and very little information
is given about why the election process keeps restarting.
> Generally improve logging to enable debuggability in the field.
> ---------------------------------------------------------------
>
> Key: ZOOKEEPER-62
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-62
> Project: Zookeeper
> Issue Type: Improvement
> Components: c client, java client, server
> Reporter: Patrick Hunt
> Assignee: Flavio Paiva Junqueira
> Attachments: zoo-log.tgz
>
>
> We need to improve our logging to enable debugging of field issues.
> Flavio, assigning to you as you are currently looking at some client/server
> issues that could benefit from better logging. Please attach patches if you
> see potential areas for improvement.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
