You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Lokesh Jain (Jira)" <ji...@apache.org> on 2021/05/31 06:59:00 UTC
[jira] [Commented] (HDDS-5278) replication manager will delete
over-replicated container with storage utilization priority
[ https://issues.apache.org/jira/browse/HDDS-5278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17354248#comment-17354248 ]
Lokesh Jain commented on HDDS-5278:
-----------------------------------
I think there is a problem with using utilisation in Replication Manager directly.
Let’s consider a scenario - container c1 and c2 with replicas in \{d1, d2, d3}. In terms of utilisation d1 > d2 > d3. Balancer schedules move c1 from d1 to d4 and c2 from d2 to d4 given there is a limit of 1 on maximum moves from a source datanode. In the Replication manager when copy is complete c1 and c2 replicas will be deleted from d1 only. Expected behavior is for c1 to be deleted from d1 and c2 to be deleted from d2.
> replication manager will delete over-replicated container with storage utilization priority
> -------------------------------------------------------------------------------------------
>
> Key: HDDS-5278
> URL: https://issues.apache.org/jira/browse/HDDS-5278
> Project: Apache Ozone
> Issue Type: Improvement
> Reporter: Jackson Yao
> Assignee: Jackson Yao
> Priority: Major
> Labels: pull-request-available
>
> when a container is over-replicated, replication manager will choose some of the replica to delete. this Jira aims that the deletion candidate replicas will be deleted by storage utilization priority
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org