You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Ethan Rose (Jira)" <ji...@apache.org> on 2021/10/20 20:34:09 UTC
[jira] [Updated] (HDDS-510) Command status should be properly
updated for ReplicateContainerCommandHandler
[ https://issues.apache.org/jira/browse/HDDS-510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ethan Rose updated HDDS-510:
----------------------------
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.
> Command status should be properly updated for ReplicateContainerCommandHandler
> ------------------------------------------------------------------------------
>
> Key: HDDS-510
> URL: https://issues.apache.org/jira/browse/HDDS-510
> Project: Apache Ozone
> Issue Type: Bug
> Components: Ozone Datanode
> Affects Versions: 0.2.1
> Reporter: Nandakumar
> Priority: Blocker
>
> In {{ReplicateContainerCommandHandler}}, we should not mark the command as success as soon as we queue ReplicationTask. We have to update it only when the task status is marked as DONE or FAILED.
> We should also make {{ReplicationSupervisor}} pool size configurable.
--
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