[
https://issues.apache.org/jira/browse/HDFS-3192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13246868#comment-13246868
]
Todd Lipcon commented on HDFS-3192:
-----------------------------------
Maybe the confusion is about readers? The one "hole" we have now is that, if
there are no writes happening on the active, then it may happily continue to
think it's active until the next write. I'd be in favor of solving this by
adding code which writes a "no-op" edit to the edit log once every second or
so. This bounds the amount of time in which it may think it's active and
respond to read requests -- since the no-op edit will cause an abort if it
loses its write access. Does that satisfy the issue you're raising?
> Active NN should exit when it has not received a getServiceStatus() rpc from
> ZKFC for timeout secs
> --------------------------------------------------------------------------------------------------
>
> Key: HDFS-3192
> URL: https://issues.apache.org/jira/browse/HDFS-3192
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: ha, name-node
> Reporter: Hari Mankude
> Assignee: Hari Mankude
>
--
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
