[ https://issues.apache.org/jira/browse/HADOOP-8212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Todd Lipcon updated HADOOP-8212: -------------------------------- Attachment: hadoop-8212.txt I fixed item #1 and #3 above. I agree the log message in #2 is a little odd, but I didn't want to duplicate the log message three times, and it felt a little excessive to factor out a "logIgnoredEvent()" call... do you have another suggestion, or is it OK to leave it? > Improve ActiveStandbyElector's behavior when session expires > ------------------------------------------------------------ > > Key: HADOOP-8212 > URL: https://issues.apache.org/jira/browse/HADOOP-8212 > Project: Hadoop Common > Issue Type: Improvement > Affects Versions: 0.23.3, 0.24.0 > Reporter: Todd Lipcon > Assignee: Todd Lipcon > Attachments: hadoop-8212.txt, hadoop-8212.txt > > > Currently when the ZK session expires, it results in a fatal error being sent > to the application callback. This is not the best behavior -- for example, in > the case of HA, if ZK goes down, we would like the current state to be > maintained, rather than causing either NN to abort. When the ZK clients are > able to reconnect, they should sort out the correct leader based on the > normal locking schemes. -- 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