[ https://issues.apache.org/jira/browse/YARN-4316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jun Gong resolved YARN-4316. ---------------------------- Resolution: Implemented > Make NM's version information useful for upgrade > ------------------------------------------------ > > Key: YARN-4316 > URL: https://issues.apache.org/jira/browse/YARN-4316 > Project: Hadoop YARN > Issue Type: Improvement > Components: nodemanager > Reporter: Jun Gong > Assignee: Jun Gong > Priority: Minor > Attachments: nodes.png > > > When upgrading all NM to a new bug fix version, we often upgrade some NM > first, then upgrade rest NM if all looks right. We could avoid breakdown > whole cluster in this way if new version of NM does not work well. But there > is no easy way to tell us whether we have missed upgrading some NM. > We could see all NM's version info in RM's web page as attached. These > version info are too generic, e.g. 2.4.1, 2.6.1, 2.6.2. For small bug fix > version, version will remain same. If we could change the version info more > detailed(e.g. 2.4.1.12), we could make sure whether we have upgrade all NM to > the new bug fix version. > I propose to add a new config(yarn.nodemanager.version) in yarn-site.xml to > solve this problem. When upgrading NM, we configure it to the new version at > the same time. NM will report this version to RM, then we could see it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)