You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Jackson Yao (Jira)" <ji...@apache.org> on 2021/06/10 09:31:00 UTC

[jira] [Created] (HDDS-5329) remove lockmanager and synchronize on containerinfo in replication manager

Jackson Yao created HDDS-5329:
---------------------------------

             Summary: remove lockmanager and synchronize on containerinfo in replication manager
                 Key: HDDS-5329
                 URL: https://issues.apache.org/jira/browse/HDDS-5329
             Project: Apache Ozone
          Issue Type: Improvement
            Reporter: Jackson Yao


 ReplicationManager has a LockManager object that creates locks based on the ContainerInfo.getContainerID().However, this lockManager is not shared with other classes in SCM. It seems to be passed into only RM.When processing a container, RM locks using this.ICRs and FCRs can change the replicas and details stored in ContainerInfo and they lock a container using synchronized(containerInfo) while processing that Container in the report.As RM and ICR/FCR use different locks the locks do not protect against changes in each other.

this Jira aims to remove LockManager from RM and just make it synchronize on the containerInfo object it is processing. 



--
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