You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Nate Cole (JIRA)" <ji...@apache.org> on 2015/08/26 22:48:54 UTC

[jira] [Updated] (AMBARI-8888) Heartbeat lost messages in ambari log after host is decommissioned, deleted and perminently powered off

     [ https://issues.apache.org/jira/browse/AMBARI-8888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nate Cole updated AMBARI-8888:
------------------------------
    Fix Version/s:     (was: 2.1.1)
                   2.1.2

> Heartbeat lost messages in ambari log after host is decommissioned, deleted and perminently powered off 
> --------------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-8888
>                 URL: https://issues.apache.org/jira/browse/AMBARI-8888
>             Project: Ambari
>          Issue Type: Story
>          Components: ambari-server
>    Affects Versions: 1.6.1
>            Reporter: Alejandro Fernandez
>            Assignee: Alejandro Fernandez
>             Fix For: 2.1.2
>
>
> Repro Steps:
> * Decommission a host
> * Delete it from the cluster
> * Poweroff the host
> * Ambari still shows that heartbeats are lost from the host
> [root@ambari hdp]# tail -f /var/log/ambari-server/ambari-server.log | grep "Heartbeat lost" 
> 11:08:33,523 WARN [Thread-1] HeartbeatMonitor:126 - Heartbeat lost from host rm.lab 
> Lab system running CentOS 6 with Ambari 1.6.1 on HDP 2.1.5 
> [root@ambari ~]# rpm -qa | grep ambari-server 
> ambari-server-1.6.1-98.noarch 
> Looks like the HeartbeatMonitor thread looks up all hosts, as opposed to only the hosts associated with the current cluster.
> This does not impact the cluster itself, but does make the logs seem misleading.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)