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=13859934#comment-13859934
] 

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

Actually, status commands are added each minute which explains the delays especially as observed
as shown above. Not sure yet why we will see a 3 minute delay. We should investigate the possibility
of updating host status after any command is executed as well.

> 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