[
https://issues.apache.org/jira/browse/HDDS-12438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17933009#comment-17933009
]
Chia-Chuan Yu commented on HDDS-12438:
--------------------------------------
Hi, [~Sammi]
I've done some analysis, are we going to put the *readlock* in
{*}OnDemandContainerReplicationSource{*}?
Hope I'm not getting it wrong, thanks!
{code:java}
public void copyData(long containerId, OutputStream destination,
CopyContainerCompression compression) {
// read lock here
Container container = controller.getContainer(containerId);
}{code}
> [DiskBalancer] Hold the old KeyValueContainer lock before copyContainer
> -----------------------------------------------------------------------
>
> Key: HDDS-12438
> URL: https://issues.apache.org/jira/browse/HDDS-12438
> Project: Apache Ozone
> Issue Type: Sub-task
> Reporter: Sammi Chen
> Assignee: Chia-Chuan Yu
> Priority: Major
>
> We should hold the read lock of old container before copyContainer, to avoid
> activities, such as block delete, and replica delete, on old container, while
> block read, container replication should best be allowed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
