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

Posted to yarn-issues@hadoop.apache.org by "Robert Parker (JIRA)" <ji...@apache.org> on 2013/08/02 21:19:50 UTC

[jira] [Updated] (YARN-819) ResourceManager and NodeManager should check for a minimum allowed version

     [ https://issues.apache.org/jira/browse/YARN-819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Parker updated YARN-819:
-------------------------------

    Attachment: YARN-819-1.patch
    
> 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, 0.23.8
>            Reporter: Robert Parker
>            Assignee: Robert Parker
>         Attachments: YARN-819-1.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