hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hairong Kuang (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-6904) A baby step towards inter-version RPC communications
Date Mon, 10 Jan 2011 22:51:48 GMT

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

Hairong Kuang updated HADOOP-6904:
----------------------------------

    Attachment: rpcCompatible-trunk5.patch

rpcCompatible-trunk5.patch incorporated Doug's review comments:
1. Fix the bug in hashCode(Method) and add a unit test for this bug;
2. Change all the method name hashCode to getFingerprint (but not the javadoc);
3. Add a cache that maps a protocol to its hashcode to optimize the repeated calculations
of the protcol's fingerprint.

> A baby step towards inter-version RPC communications
> ----------------------------------------------------
>
>                 Key: HADOOP-6904
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6904
>             Project: Hadoop Common
>          Issue Type: New Feature
>          Components: ipc
>    Affects Versions: 0.22.0
>            Reporter: Hairong Kuang
>            Assignee: Hairong Kuang
>             Fix For: 0.23.0
>
>         Attachments: majorMinorVersion.patch, majorMinorVersion1.patch, rpcCompatible-trunk.patch,
rpcCompatible-trunk1.patch, rpcCompatible-trunk2.patch, rpcCompatible-trunk4.patch, rpcCompatible-trunk5.patch,
rpcVersion.patch, rpcVersion1.patch
>
>
> Currently RPC communications in Hadoop is very strict. If a client has a different version
from that of the server, a VersionMismatched exception is thrown and the client can not connect
to the server. This force us to update both client and server all at once if a RPC protocol
is changed. But sometime different versions do not mean the client & server are not compatible.
It would be nice if we could relax this restriction and allows us to support inter-version
communications.
> My idea is that DfsClient catches VersionMismatched exception when it connects to NameNode.
It then checks if the client & the server is compatible. If yes, it sets the NameNode
version in the dfs client and allows the client to continue talking to NameNode. Otherwise,
rethrow the VersionMismatch exception.

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