[
https://issues.apache.org/jira/browse/HDDS-4731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17271576#comment-17271576
]
Xiaoyu Yao commented on HDDS-4731:
----------------------------------
This is a forward compatibility issue where the old client can't handle the new
DatanodeDetails.Port.Name (REPLICATION) added by HDDS-4496. The protoc from
hdds.proto does not change, that's why the compatibility checker won't catch
it. It can be handled at code level to make this change forward compatible in
DatanodeDetails#getFromProtoBuf().
> Fix compatibility issue caused by new add enum
> DatanodeDetails.Port.Name.REPLICATION
> ------------------------------------------------------------------------------------
>
> Key: HDDS-4731
> URL: https://issues.apache.org/jira/browse/HDDS-4731
> Project: Hadoop Distributed Data Store
> Issue Type: Bug
> Components: Ozone Datanode
> Reporter: Glen Geng
> Assignee: Attila Doroszlai
> Priority: Blocker
> Attachments: 截屏2021-01-21 下午7.24.01.png
>
>
> In tencent, we monthly deploy latest master to our production environment.
> When running an upgrade test from old ozone version (at Dec 14 2020) to new
> ozone version (at Jun 14 2021), testDFSIO using jars of old ozone can not
> write to the new ozone cluster, met the error that
> No enum constant
> org.apache.hadoop.hdds.protocol.DatanodeDetails.Port.Name.REPLICATION
> We consider it is related to HDDS-4496. Separate client and server2server
> GRPC services of datanode.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
