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

["Prashant Pogde (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HDDS-962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Prashant Pogde updated HDDS-962:
--------------------------------
    Target Version/s: 1.2.0

I am managing the 1.1.0 release and we currently have more than 600 issues targeted for 1.1.0. I am moving the target field to 1.2.0. 

If you are actively working on this jira and believe this should be targeted to 1.1.0 release, Please change the target field back to 1.1.0 before Feb 05, 2021. 

> Introduce locking for container operations that are executed via DatanodeCommand
> --------------------------------------------------------------------------------
>
>                 Key: HDDS-962
>                 URL: https://issues.apache.org/jira/browse/HDDS-962
>             Project: Hadoop Distributed Data Store
>          Issue Type: Improvement
>          Components: Ozone Datanode
>            Reporter: Nanda kumar
>            Assignee: Nanda kumar
>            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.3.4#803005)

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