[jira] [Updated] (HDDS-67) Add priority for datanode commands in SCM

["Ethan Rose (Jira)" <ji...@apache.org>]

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

Ethan Rose updated HDDS-67:
---------------------------
    Target Version/s: 1.3.0  (was: 1.2.0)

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

If you are actively working on this jira and believe this should be targeted for the 1.2.0 release, Please reach out to me via Apache email or Slack.

> Add priority for datanode commands in SCM
> -----------------------------------------
>
>                 Key: HDDS-67
>                 URL: https://issues.apache.org/jira/browse/HDDS-67
>             Project: Apache Ozone
>          Issue Type: Bug
>          Components: SCM
>            Reporter: Anu Engineer
>            Assignee: Lokesh Jain
>            Priority: Major
>
> While reviewing HDFS-11493, [~cheersyang] commented that it would be a good idea to support priority for datanode commands send from SCM.
> bq. The queue seems to be time ordered, I think it will be better to support priority as well. Commands may have different priority, for example, replicate a container priority is usually higher than delete a container replica; replicate a container also may have different priorities according to the number of replicas 
> This jira tracks that work item.



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