[
https://issues.apache.org/jira/browse/HDFS-892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doug Cutting updated HDFS-892:
------------------------------
Attachment: HDFS-892.patch
> all the changes are compatible changes except renaming register(..) to
> registerDatanode(..) in DatanodeProtocol. So the protocol version have to be
> updated.
Thanks for catching that! I've attached a new version that updates this.
> Do we need a versionID for the new NamenodeProtocols?
I don't think so, clients are not permitted to use that interface. NameNode's
getProtocolVersion() implementation dispatches depending on the client's
protocol. If a client tried to connect using the NamenodeProtocols interface,
then that method will fail with "unknown protocol".
> optionally use Avro for namenode RPC
> ------------------------------------
>
> Key: HDFS-892
> URL: https://issues.apache.org/jira/browse/HDFS-892
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: name-node
> Reporter: Doug Cutting
> Assignee: Doug Cutting
> Fix For: 0.22.0
>
> Attachments: HDFS-892.patch, HDFS-892.patch, HDFS-892.patch,
> HDFS-892.patch, HDFS-892.patch, HDFS-892.patch
>
>
> It should be possible to configure HDFS so that Avro is used for RPCs to the
> namenode.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
