[
https://issues.apache.org/jira/browse/HADOOP-9545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13653526#comment-13653526
]
Todd Lipcon commented on HADOOP-9545:
-------------------------------------
I did eventually diagnose the issue here, and it turned out to be a ZK server
side bug in which the different ZK servers had gotten out of sync with each
other. So ZKFC was actually doing the right thing. But yep, I still want to
bump the logging -- further logging would have made it far more obvious that ZK
was at fault here rather than a ZKFC issue. Thanks for the pointer to
ZOOKEEPER-1702, though.
> Improve logging in ActiveStandbyElector
> ---------------------------------------
>
> Key: HADOOP-9545
> URL: https://issues.apache.org/jira/browse/HADOOP-9545
> Project: Hadoop Common
> Issue Type: Improvement
> Components: auto-failover, ha
> Affects Versions: 2.0.5-beta
> Reporter: Todd Lipcon
> Assignee: Todd Lipcon
> Priority: Minor
>
> The ActiveStandbyElector currently logs a lot of stuff at DEBUG level which
> would be useful for troubleshooting. We've seen one instance in the wild of a
> ZKFC thinking it should be in standby state when in fact it won the election,
> but the logging is insufficient to understand why. I'd like to bump most of
> the existing DEBUG logs to INFO and add some additional logs as well.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
