[
https://issues.apache.org/jira/browse/HDDS-13086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aswin Shakil updated HDDS-13086:
--------------------------------
Status: Patch Available (was: Open)
> Block duplicate reconciliation requests for the same container and datanode
> within the datanode
> -----------------------------------------------------------------------------------------------
>
> Key: HDDS-13086
> URL: https://issues.apache.org/jira/browse/HDDS-13086
> Project: Apache Ozone
> Issue Type: Sub-task
> Reporter: Ethan Rose
> Assignee: Aswin Shakil
> Priority: Major
> Labels: pull-request-available
>
> Dedup of replication commands like reconciliation is handled by the
> [ReplicationSupervisor|https://github.com/apache/ozone/blob/1aef378d70f11ed7523c397903b3a26edf93c635/hadoop-hdds/container-service/src/main/java/org/apache/hadoop/ozone/container/replication/ReplicationSupervisor.java#L98]
> and tested generally
> [here|https://github.com/apache/ozone/blob/2b4708b70e5c9de133381a38ca7fa4b3cf3caa42/hadoop-hdds/container-service/src/test/java/org/apache/hadoop/ozone/container/replication/TestReplicationSupervisor.java#L558].
> However this depends on how we define the uniqueness of the reconciliation
> commands. We can get multiple simultaneous reconciliation tasks for the same
> container [if the peer list is
> different|https://github.com/apache/ozone/blob/989746a0de358267be31ce81824046766b49bb7c/hadoop-hdds/container-service/src/main/java/org/apache/hadoop/ozone/protocol/commands/ReconcileContainerCommand.java#L98]
> which could lead to undesired simultaneous container updates. We should fix
> this so that ReconcileContainerCommand equality is based only on container
> ID, and add a test for this that is unique to reconciliation commands.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
