[ https://issues.apache.org/jira/browse/AMBARI-24416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Onischuk updated AMBARI-24416: ------------------------------------- Attachment: AMBARI-24416.patch > Component Versions Are Not Reported On Initial Status Commands Anymore > ---------------------------------------------------------------------- > > Key: AMBARI-24416 > URL: https://issues.apache.org/jira/browse/AMBARI-24416 > Project: Ambari > Issue Type: Bug > Reporter: Andrew Onischuk > Assignee: Andrew Onischuk > Priority: Major > Fix For: 2.7.1 > > Attachments: AMBARI-24416.patch > > > In Ambari 2.6, some status commands were able to supply the version of the > component they were running for. This was needed especially during upgrades to > correct situations where components would fail to start but the processes were > actually running and reporting. > * During heartbeat registration, Ambari asked the agent to get the version > in the next status command: > <https://github.com/apache/ambari/blob/branch-2.6/ambari- > server/src/main/java/org/apache/ambari/server/agent/HeartBeatHandler.java#L416-L419> > * The status command would place the version information from the > structured out into the "extra" mapping, which would then be handled here via > an event: > <https://github.com/apache/ambari/blob/trunk/ambari- > server/src/main/java/org/apache/ambari/server/agent/HeartbeatProcessor.java#L599-L603> > We need to replace this functionality so that component versions are reported > on registration of agents. -- This message was sent by Atlassian JIRA (v7.6.3#76005)