[ 
https://issues.apache.org/jira/browse/HDDS-2?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16459484#comment-16459484
 ] 

Bharat Viswanadham edited comment on HDDS-2 at 5/1/18 6:48 AM:
---------------------------------------------------------------

Fixed testcase failure in TestNodeManagerChillMode and also fixed findbug 
warnings.

As for other test cases failure, chill mode exit will happen when we receive a 
sendcontainerReport, this will happen after the heartbeat is processed.  In 
HDDS-3 Jira, this logic is changed to send container report in register call. 
So I think if that Jira goes in, the test case issue will be resolved.


was (Author: bharatviswa):
Fixed testcase failure in TestNodeManagerChillMode and also fixed findbug 
warnings.

As for other test cases failure, chill mode exit will happen when we receive a 
sendcontainerReport, this will happen after the heartbeat is processed.  In 
HDDS-3 Jira, this logic is changed to send container report in register call. 
So I think if that Jira goes in the issue will be resolved.

> Chill Mode to consider percentage of container reports
> ------------------------------------------------------
>
>                 Key: HDDS-2
>                 URL: https://issues.apache.org/jira/browse/HDDS-2
>             Project: Hadoop Distributed Data Store
>          Issue Type: Task
>          Components: SCM
>            Reporter: Bharat Viswanadham
>            Assignee: Bharat Viswanadham
>            Priority: Major
>             Fix For: 0.2.1
>
>         Attachments: Chill Mode.pdf, HDDS-02.002.patch, HDDS-02.003.patch, 
> HDFS-13500.00.patch, HDFS-13500.01.patch, HDFS-13500.02.patch
>
>
> To come out of chill mode currenly if one datanode is registered, we come out 
> of chill mode in SCM.
> This needs to be changed to consider percentage of container reports.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to