[
https://issues.apache.org/jira/browse/HDDS-15614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18090705#comment-18090705
]
Ethan Rose commented on HDDS-15614:
-----------------------------------
Sure, thanks for the reply. Considering this path has been off by default for
three years I don't think it is premature to remove it. On the ZDU replication
path, both the client and server need to operate on the same apparent version
to provide agreement on the API while datanodes are in mixed versions. Tracking
this version requires twice the work when there are two protocols that have
different client and server roles.
By removing the API before ZDU we do not need to do any compatibility handling,
since the cluster must be upgraded to the first ZDU enabled version before it
can use ZDU for upgrades going forward. If we remove it after ZDU, we will need
to take precautions to make sure the replications don't fail as datanodes are
being upgraded. For this feature specifically, it did ship with a feature flag
before ZDU support which helps. We could delete the pull replicator and add a
release note that any override of the pull replication config must be removed
before doing ZDU. However, making this work out of the box without a release
note would be preferred, which would require us to remove it now.
> Remove Datanode download/pull container replication
> ---------------------------------------------------
>
> Key: HDDS-15614
> URL: https://issues.apache.org/jira/browse/HDDS-15614
> Project: Apache Ozone
> Issue Type: Improvement
> Components: Ozone Datanode
> Reporter: Ethan Rose
> Assignee: Ethan Rose
> Priority: Major
>
> Datanodes have used push replication to move containers by default since
> early 2023. There is no reason to continue using the pull model which is now
> disabled behind a feature flag. We can safely remove it, which will be easier
> to do before ZDU is merged into master.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
