[
https://issues.apache.org/jira/browse/HDDS-1196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16781108#comment-16781108
]
Anu Engineer commented on HDDS-1196:
------------------------------------
bq. when we are out of chill mode, we set replication enabled.
Why is this not enough? if the Chill Mode manager said we are done waiting do
we need to additional wait?
> Add a ReplicationStartTimer class
> ----------------------------------
>
> Key: HDDS-1196
> URL: https://issues.apache.org/jira/browse/HDDS-1196
> Project: Hadoop Distributed Data Store
> Issue Type: Bug
> Components: SCM
> Reporter: Bharat Viswanadham
> Assignee: Bharat Viswanadham
> Priority: Major
>
> Condition for to Start Replication monitor thread.
> # Exit Chill mode
> # Time out (configurable value) default to 5 minutes. Additional time out is
> added to give some additional time for datanodes to report and make pipelines
> healthy.
> So, once we are out of chillmode, we fire ChillModeStatus, this
> ReplicationTimer Class will listen to that event, and wait for a configurable
> time, and then emit replicationEnabled.
>
> The current code, when we are out of chill mode, we set replication enabled.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
