hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron T. Myers (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-2811) HA: Client should fail if a failover occurs which switches block pool ID
Date Mon, 30 Jan 2012 20:59:10 GMT

    [ https://issues.apache.org/jira/browse/HDFS-2811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13196412#comment-13196412
] 

Aaron T. Myers commented on HDFS-2811:
--------------------------------------

bq. Using block pool ID which should be opaque to the client (and garbage in/garbage out)
for detecting misconfiguration does not seem correct. The only reliable identifier a client
uses is that of a file URI. If same namespace is supported on two namenodes with federation
(very unlikely) then adding checks like block pool ID is not fool proof. You might have client
failover before even discovering the block pool ID from the first namenode and hence continues
to use wrong namenode.

That seems reasonable to me. Feel free to close this issue, if you'd like, or re-purpose it
to try validate HA configuration.

BTW, this is the JIRA which prompted this JIRA to be filed: HDFS-2367
                
> 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

        

Mime
View raw message