hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Doug Cutting (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HDFS-1335) HDFS side of HADOOP-6904: first step towards inter-version communications between dfs client and NameNode
Date Mon, 09 Aug 2010 18:27:16 GMT

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

Doug Cutting commented on HDFS-1335:
------------------------------------

If I understand the patch correctly, it still requires an exact version match by default.
 That seems good.  What I don't understand is how you expect that to be altered.  Do you expect
folks to update the implementation of ProtocolCompatible as protocols evolve?  Perhaps you
can give some examples of how you expect this to work?

Since there's more than one protocol in HDFS, do you expect to add more methods to ProtocolCompatible
for each protocol?

> HDFS side of HADOOP-6904: first step towards inter-version communications between dfs
client and NameNode
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: HDFS-1335
>                 URL: https://issues.apache.org/jira/browse/HDFS-1335
>             Project: Hadoop HDFS
>          Issue Type: New Feature
>          Components: hdfs client, name-node
>    Affects Versions: 0.22.0
>            Reporter: Hairong Kuang
>            Assignee: Hairong Kuang
>             Fix For: 0.22.0
>
>         Attachments: hdfsRpcVersion.patch
>
>
> The idea is that for getProtocolVersion, NameNode checks if the client and server versions
are compatible if the server version is greater than the client version. If no, throws a VersionIncompatible
exception; otherwise, returns the server version.
> On the dfs client side, when creating a NameNode proxy, catches the VersionMismatch exception
and then checks if the client version and the server version are compatible if the client
version is greater than the server version. If not compatible, throws exception VersionIncomptible;
otherwise, records the server version and continues.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message