[jira] [Updated] (HDFS-2627) HA: determine DN's view of which NN is active based on heartbeat responses

["Todd Lipcon (Updated) (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HDFS-2627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Todd Lipcon updated HDFS-2627:
------------------------------

    Attachment: hdfs-2627-v1.txt

Here's a v1 patch. Needs a little bit more cleanup/javadoc before commit, but worth doing a big-picture review now if someone has cycles.
                
> HA: determine DN's view of which NN is active based on heartbeat responses
> --------------------------------------------------------------------------
>
>                 Key: HDFS-2627
>                 URL: https://issues.apache.org/jira/browse/HDFS-2627
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: data-node, ha, name-node
>    Affects Versions: HA branch (HDFS-1623)
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>         Attachments: hdfs-2627-v1.txt
>
>
> This is the first part of the design described in [this comment|https://issues.apache.org/jira/browse/HDFS-1972?focusedCommentId=13160601&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13160601] in HDFS-1972. When the DNs start, they should not consider either of the NNs in a block pool to be the active one. Rather, the NNs should include their HA state as part of the heartbeat response to the DN, and the DN will believe whichever NN claims to be active at a higher transaction ID.

--
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