[
https://issues.apache.org/jira/browse/HDDS-895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nanda kumar updated HDDS-895:
-----------------------------
Description:
We can remove the command watcher from {{ReplicationManager}} and user internal
timeout to retrigger the replication command.
Instead of waiting for every command that has been sent out to datanode, we can
use an internal timer to check if the container replica state has reached the
expected container state.
was:We can remove the command watcher from {{ReplicationManager}} and user
internal timeout to retrigger the replication command.
> Remove command watcher from ReplicationManager
> ----------------------------------------------
>
> Key: HDDS-895
> URL: https://issues.apache.org/jira/browse/HDDS-895
> Project: Hadoop Distributed Data Store
> Issue Type: Improvement
> Components: SCM
> Reporter: Nanda kumar
> Assignee: Nanda kumar
> Priority: Major
> Attachments: HDDS-895.000.patch
>
>
> We can remove the command watcher from {{ReplicationManager}} and user
> internal timeout to retrigger the replication command.
> Instead of waiting for every command that has been sent out to datanode, we
> can use an internal timer to check if the container replica state has reached
> the expected container state.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
