[jira] [Updated] (HDDS-15641) SCM should send write pipeline version with DatanodeDetails on block allocation

["Zita Dombi (Jira)" <ji...@apache.org>]

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

Zita Dombi updated HDDS-15641:
------------------------------
    Resolution: Fixed
        Status: Resolved  (was: Patch Available)

> SCM should send write pipeline version with DatanodeDetails on block allocation
> -------------------------------------------------------------------------------
>
>                 Key: HDDS-15641
>                 URL: https://issues.apache.org/jira/browse/HDDS-15641
>             Project: Apache Ozone
>          Issue Type: Improvement
>            Reporter: Zita Dombi
>            Assignee: Zita Dombi
>            Priority: Major
>              Labels: pull-request-available
>
> Instead of forwarding the Datanode's software version like it does currently, SCM should forward the apparent version to use for writes based on the cluster's finalization status. The DatanodeDetails object currently has two version fields: currentVersion tracks the Datanode's software version, and initialVersion tracks the software version it was first initialized with. We will need to decide whether we should repopulate currentVersion with the pipeline version at SCM before giving the datanodeDetails to the client, or if we should create a new field for pipeline version. Note that old clients will be deserializing the currentVersion field from the proto to use for server side versioning checks already.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org