You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Arpit Agarwal (Jira)" <ji...@apache.org> on 2020/06/01 01:16:00 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 ]
Arpit Agarwal updated HDDS-510:
-------------------------------
Target Version/s: 0.6.0 (was: 0.5.0)
Labels: TriagePending (was: )
[~nanda] this seems like a must fix for 0.6.0. Can you confirm?
> Command status should be properly updated for ReplicateContainerCommandHandler
> ------------------------------------------------------------------------------
>
> Key: HDDS-510
> URL: https://issues.apache.org/jira/browse/HDDS-510
> Project: Hadoop Distributed Data Store
> Issue Type: Bug
> Components: Ozone Datanode
> Affects Versions: 0.2.1
> Reporter: Nanda kumar
> Priority: Major
> Labels: TriagePending
>
> 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: ozone-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: ozone-issues-help@hadoop.apache.org