ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-18835) Heartbeat lost for all hosts after server start
Date Wed, 09 Nov 2016 22:54:00 GMT

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

Hudson commented on AMBARI-18835:
---------------------------------

SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #5975 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5975/])
AMBARI-18835. Heartbeat lost for all hosts after server start. (swagle: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=620329c5b272a17bdeb4495f46834c903d0b23d3])
* (edit) ambari-server/src/main/java/org/apache/ambari/server/state/alert/AlertDefinitionHash.java


> Heartbeat lost for all hosts after server start
> -----------------------------------------------
>
>                 Key: AMBARI-18835
>                 URL: https://issues.apache.org/jira/browse/AMBARI-18835
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.0.0
>            Reporter: Myroslav Papirkovskyi
>            Assignee: Myroslav Papirkovskyi
>             Fix For: 2.4.2
>
>         Attachments: AMBARI-18835.patch
>
>
> Occurred once after upgrade. REST endpoints for agents became inaccessible and agents
were unable to send heartbeats.
> Research has shown that all jetty worker threads were in infinite loop while reading
from HashMap which was not threadsafe.



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

Mime
View raw message