HDDS-8368. ReplicationManager: Create ContainerReplicaOp with correct target Datanode #4532
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What changes were proposed in this pull request?
ReplicationManager
createsContainerReplicaOp
inadjustPendingOpsAndMetrics
. For replicate command, the target datanode in theop
should be the datanode that reports back addition of a replica. However currently the target datanode is being set as the datanode that the command is being sent to. This PR fixes this.What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-8368
How was this patch tested?
Added UT.
Draft because I'm waiting for CI in my fork: https://github.com/siddhantsangwan/ozone/actions/runs/4607466302