hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daryn Sharp (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-3556) Allow non-HA clients to use HA tokens
Date Fri, 22 Jun 2012 14:11:42 GMT

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

Daryn Sharp commented on HDFS-3556:
-----------------------------------

If the tokens contained the real host's service instead of the specially encoded logical uri,
then the token would usable by both HA and non-HA client.  Granted, the non-HA client will
not be able to use the token if a failover occurs.  Hopefully that's a rare event that is
outweighed by the additional compatibility this change offers.

The ability to provide this implementation hinges on NN proxy creation attempting to reverse-map
a given NN's authority into its HA logical name, instead of simply checking if the uri's host
is a HA logical name.  Otherwise token renew/cancel will be bound to the origin NN even after
failover occurs.

No changes would be required to non-HA clients, the current specialized HA token service handling
can be removed, and enabling/disabling HA for an existing NN becomes transparent to users.

Please provide comments on this approach.
                
> Allow non-HA clients to use HA tokens
> -------------------------------------
>
>                 Key: HDFS-3556
>                 URL: https://issues.apache.org/jira/browse/HDFS-3556
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: ha
>    Affects Versions: 2.0.0-alpha, 3.0.0
>            Reporter: Daryn Sharp
>            Assignee: Daryn Sharp
>
> HA tokens contain a "non-standard" service that encodes the logical uri.  This prevents
HA tokens from being usable by a non-HA configured client.

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