You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Myroslav Papirkovskyy (JIRA)" <ji...@apache.org> on 2016/02/23 14:44:18 UTC

[jira] [Updated] (AMBARI-15141) Start all services request aborts in the middle and hosts go into heartbeat-lost state

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

Myroslav Papirkovskyy updated AMBARI-15141:
-------------------------------------------
    Attachment: AMBARI-15141.patch
                AMBARI-15141_branch-2.2.patch

> Start all services request aborts in the middle and hosts go into heartbeat-lost state
> --------------------------------------------------------------------------------------
>
>                 Key: AMBARI-15141
>                 URL: https://issues.apache.org/jira/browse/AMBARI-15141
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.2.0
>            Reporter: Myroslav Papirkovskyy
>            Assignee: Myroslav Papirkovskyy
>            Priority: Critical
>             Fix For: 2.2.2
>
>         Attachments: AMBARI-15141.patch, AMBARI-15141_branch-2.2.patch
>
>
> On the 1600 node cluster I attempted to do Stop-All and Start-All actions. During both actions, the request would abort itself - sometimes even when there were no failures or timeouts. Also, during this time hosts would go into heartbeat-lost state and the cluster would look like its broken. After like 5-10 minutes, the hosts slowly come back online and correct host-status is got. But due to request abort, some components would be stopped/started when they should not be.



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