You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ozone.apache.org by "mingchao zhao (Jira)" <ji...@apache.org> on 2022/12/21 09:56:00 UTC

[jira] [Commented] (HDDS-962) Introduce locking for container operations that are executed via DatanodeCommand

    [ https://issues.apache.org/jira/browse/HDDS-962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17650709#comment-17650709 ] 

mingchao zhao commented on HDDS-962:
------------------------------------

Ozone 1.3.0 had been released and we currently have more than 600 open issues targeted for 1.3.0. I am moving the target field to 1.4.0.

If there is anything needs to be discussed about the Target Version, Please reach out to me via Apache email or Slack.

> Introduce locking for container operations that are executed via DatanodeCommand
> --------------------------------------------------------------------------------
>
>                 Key: HDDS-962
>                 URL: https://issues.apache.org/jira/browse/HDDS-962
>             Project: Apache Ozone
>          Issue Type: Improvement
>          Components: Ozone Datanode
>            Reporter: Nandakumar
>            Assignee: Nandakumar
>            Priority: Major
>
> When SCM decides to take some action on a container, it sends DatanodeCommand to the datanodes. These commands are handled by CommandHandlers in datanode. Without proper locking, we cannot process these commands in parallel. This jira aims to introduce locks on container operations which are performed via ContainerController.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org