[
https://issues.apache.org/jira/browse/YARN-819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13775697#comment-13775697
]
Robert Parker commented on YARN-819:
------------------------------------
Jon, Thanks for the review and nice catch on branch-2.
* Changed the TestResourceTrackerService#testNodeRegistrationVersionLessThanRM
test case to run on branch-2 and greater.
* The jira mentions reboot as on option. A reboot would cover the case where
new software is deployed but the NM process is not restarted. There is no
guarantee that the new version can talk to the older version so rejection of
the connection will satisfy the requirement and is much less complicated.
* Corrected the other three code issues.
> ResourceManager and NodeManager should check for a minimum allowed version
> --------------------------------------------------------------------------
>
> Key: YARN-819
> URL: https://issues.apache.org/jira/browse/YARN-819
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: nodemanager, resourcemanager
> Affects Versions: 2.0.4-alpha
> Reporter: Robert Parker
> Assignee: Robert Parker
> Attachments: YARN-819-1.patch, YARN-819-2.patch, YARN-819-3.patch
>
>
> Our use case is during upgrade on a large cluster several NodeManagers may
> not restart with the new version. Once the RM comes back up the NodeManager
> will re-register without issue to the RM.
> The NM should report the version the RM. The RM should have a configuration
> to disallow the check (default), equal to the RM (to prevent config change
> for each release), equal to or greater than RM (to allow NM upgrades), and
> finally an explicit version or version range.
> The RM should also have an configuration on how to treat the mismatch:
> REJECT, or REBOOT the NM.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
