[ https://issues.apache.org/jira/browse/AMBARI-24669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jayush Luniya reopened AMBARI-24669: ------------------------------------ > 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 > Priority: Blocker > Labels: pull-request-available > Fix For: 2.8.0 > > Time Spent: 40m > Remaining Estimate: 0h > > 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)