ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sumit Mohanty (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-4206) Significant lag between host status update and slave/master component start/stop
Date Wed, 01 Jan 2014 19:57:50 GMT

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

Sumit Mohanty commented on AMBARI-4206:
---------------------------------------

UI checks the host_status from the server at an interval of 6 seconds (host component status
are updated simultaneously in the same polling run).
The server updates the host_status on every heartbea (should happen about every 10 seconds).
Here are the result of 10 test runs, measuring the time between the host component status
update and host status update.  Note that these are multiples of 6's because UI polls every
6 seconds:

30
12
12
12
12
30
6
0
6
0



> Significant lag between host status update and slave/master component start/stop
> --------------------------------------------------------------------------------
>
>                 Key: AMBARI-4206
>                 URL: https://issues.apache.org/jira/browse/AMBARI-4206
>             Project: Ambari
>          Issue Type: Bug
>          Components: controller
>    Affects Versions: 1.4.3
>            Reporter: Sumit Mohanty
>            Assignee: Sumit Mohanty
>             Fix For: 1.4.3
>
>
> Steps:
> # Go to any host with slave component (DataNode, for example).
> # Click "Stop" options for slave component.
> Result: status marker for slave component start blinking red, but status marker for host
behaves strangely: sometimes it also start blinking red immediately/ sometimes changes status
to not-blinking red only after slave component stopping will be ended.
> The same for slave component starting.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message