sodonnel commented on code in PR #3836:
URL: https://github.com/apache/ozone/pull/3836#discussion_r1001691313
##########
hadoop-hdds/server-scm/src/main/java/org/apache/hadoop/hdds/scm/container/replication/ECUnderReplicationHandler.java:
##########
@@ -353,8 +386,77 @@ private void processMaintenanceOnlyIndexes(
DatanodeDetails target = iterator.next();
commands.put(target, replicateCommand);
additionalMaintenanceCopiesNeeded -= 1;
+ maintIndexes.remove(replica.getReplicaIndex());
+ createdIndexes.add(replica.getReplicaIndex());
+ }
+ }
+ }
+
+ /**
+ * Function processes Replicas to fix placement policy issues.
+ * @param replicas
+ * @param deletionInFlight
+ * @param container
+ * @param excludedNodes
+ * @param sources
+ * @param createdIndexes
+ * @param placementStatus
+ * @throws IOException
+ */
+ private Map<DatanodeDetails, SCMCommand<?>> processMisreplication(
+ Set<ContainerReplica> replicas,
+ List<DatanodeDetails> deletionInFlight, ContainerInfo container,
+ List<DatanodeDetails> excludedNodes,
+ Map<Integer, Pair<ContainerReplica, NodeStatus>> sources,
+ Set<Integer> createdIndexes, ContainerPlacementStatus
placementStatus)
+ throws IOException {
+ if (placementStatus.isPolicySatisfied() ||
+ placementStatus.misReplicationCount() <= createdIndexes.size()) {
+ return Collections.emptyMap();
+ }
+ Map<DatanodeDetails, SCMCommand<?>> commands = new HashMap<>();
+ List<Integer> sortedReplicaIdx =
Review Comment:
I'm not sure what this is doing? Are we sorting the replicas so that if we
have say, 2 copies of index 3, it will be first in the list?
To fix mis-replication, we must have some indexes that reside on the same
rack. So if we find a new node on a new rack, a candidate index to move is one
where there are multiple indexes on the same rack. So I think we need to find
any indexes that reside on the same rack and then move one of them to the new
target.
Note there could be 2 or more on the same rack.
--
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]
