You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ambari.apache.org by "Myroslav Papirkovskyi (JIRA)" <ji...@apache.org> on 2018/09/20 14:11:00 UTC

[jira] [Created] (AMBARI-24669) Component status can stuck in starting/stopping status on heartbeat lost

Myroslav Papirkovskyi created AMBARI-24669:
----------------------------------------------

             Summary: Component status can stuck in starting/stopping status on heartbeat lost
                 Key: AMBARI-24669
                 URL: https://issues.apache.org/jira/browse/AMBARI-24669
             Project: Ambari
          Issue Type: Bug
          Components: ambari-agent, ambari-server
    Affects Versions: 2.7.0
            Reporter: Myroslav Papirkovskyi
            Assignee: Myroslav Papirkovskyi
             Fix For: 2.8.0


Now server sets components statuses to UNKNOWN and saves last actual state on heartbeat lost. After agent re-registering server restores saved state, but in case "in progress" state request is already aborted and agent status updates can not be applied. Agent should always send component statuses after registering, not only on status changes. Also last actual state logic should be removed. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)