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

Wei-Chiu Chuang reassigned HDDS-9884:
-------------------------------------

    Assignee: Siyao Meng

> DataNode doesn't set proper DatanodeVersion when registering with SCM
> ---------------------------------------------------------------------
>
>                 Key: HDDS-9884
>                 URL: https://issues.apache.org/jira/browse/HDDS-9884
>             Project: Apache Ozone
>          Issue Type: Sub-task
>            Reporter: Wei-Chiu Chuang
>            Assignee: Siyao Meng
>            Priority: Major
>
> DataNode has a version defined by DatanodeVersion. This is different from 
> ContainerLayoutVersion,
> HDDSVolumeLayoutVersion or HDDSLayoutFeature.
>  
> DatanodeVersion is supposed to be carrried inside DatanodeDetails 
> (initialVersion and currentVersion) but they are not when Datanode register 
> with SCM, so SCM doesn't know the DataNode version. Therefore, client doesn't 
> know.
>  
> This would need to be fixed to allow new clients talking to old DataNode 
> without blowing up old DataNode. New clients should be able to tell the 
> DataNodes are old and do not send new types of requests.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to