You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-dev@hadoop.apache.org by "Aaron T. Myers (Created) (JIRA)" <ji...@apache.org> on 2012/01/19 20:30:40 UTC

[jira] [Created] (HDFS-2811) HA: Client should fail if a failover occurs which switches block pool ID

HA: Client should fail if a failover occurs which switches block pool ID
------------------------------------------------------------------------

                 Key: HDFS-2811
                 URL: https://issues.apache.org/jira/browse/HDFS-2811
             Project: Hadoop HDFS
          Issue Type: Sub-task
          Components: ha, hdfs client, name-node
    Affects Versions: HA branch (HDFS-1623)
            Reporter: Aaron T. Myers


Making sure that the client is talking to an NN with the same block pool ID as the one it was previously talking to seems like a good sanity check.

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

        

[jira] [Resolved] (HDFS-2811) HA: Client should fail if a failover occurs which switches block pool ID

Posted by "Brandon Li (Resolved) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HDFS-2811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brandon Li resolved HDFS-2811.
------------------------------

    Resolution: Invalid

As it was pointed out, the client should not be aware of the block pool ID, and even it did, the verification on client side is hard to be fool proof. Close it as not a problem.

                
> HA: Client should fail if a failover occurs which switches block pool ID
> ------------------------------------------------------------------------
>
>                 Key: HDFS-2811
>                 URL: https://issues.apache.org/jira/browse/HDFS-2811
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: ha, hdfs client, name-node
>    Affects Versions: HA branch (HDFS-1623)
>            Reporter: Aaron T. Myers
>            Assignee: Brandon Li
>
> Making sure that the client is talking to an NN with the same block pool ID as the one it was previously talking to seems like a good sanity check.

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