sodonnel commented on code in PR #4099:
URL: https://github.com/apache/ozone/pull/4099#discussion_r1051159697
##########
hadoop-hdds/server-scm/src/main/java/org/apache/hadoop/hdds/scm/container/replication/ContainerHealthResult.java:
##########
@@ -207,19 +215,28 @@ public boolean isUnrecoverable() {
* containers are not spread across enough racks.
*/
public static class MisReplicatedHealthResult
- extends ContainerHealthResult {
+ extends UnderReplicatedHealthResult {
- private final boolean replicatedOkAfterPending;
+ /**
+ * In UnderReplicatedHealthState, DECOMMISSION_REDUNDANCY is defined as
+ * 5 so that containers which are really under replicated get fixed as a
+ * priority over decommissioning hosts. We have defined that a container
+ * can only be mis replicated if it is not over or under replicated. Fixing
+ * mis replication is arguably less important than competing a
decommission.
+ * So as a lot of mis replicated container do not block decommission, we
+ * set the redundancy of mis replicated containers to 6 so they sort after
+ * under / over replicated and decommissioning replicas in the under
+ * replication queue.
+ */
+ private static final int MIS_REP_REDUNDANCY = 6;
Review Comment:
I'm not really convinced that mis-rep count really means much and it is
worth ordering them further, as the container already has enough replicas. We
want these to start with a lower priority than anything else (under rep,
decommission), which setting it to 6 does. After that, we can only lower the
priority further. If we have a mis rep count of 1 or 2 for a 3-2 and a 6-3
container, which is higher priority? I'm not sure about a good way to do this.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
