[
https://issues.apache.org/jira/browse/HDDS-15614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18090654#comment-18090654
]
Ivan Andika edited comment on HDDS-15614 at 6/22/26 3:53 PM:
-------------------------------------------------------------
[~erose] I agree that the project direction should not be dictated on internal
use cases. The main question is whether this removal is premature. If it is
blocking features like ZDU, I'm +1 on removing this (apologies since I'm not
familiar with ZDU flow so you might need to explain a bit). Otherwise, it
doesn't hurt to defer this.
was (Author: JIRAUSER298977):
[~erose] I agree that the project direction should not be dictated on internal
use cases. The main question is whether this removal is premature. If it is
blocking features like ZDU, I'm +1 on removing this. Otherwise, it doesn't hurt
to defer this.
> 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]
