hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Yang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-7939) Yarn Service Upgrade: add support to upgrade a component instance
Date Wed, 28 Mar 2018 20:37:00 GMT

    [ https://issues.apache.org/jira/browse/YARN-7939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16418070#comment-16418070

Eric Yang commented on YARN-7939:

[~csingh] It would be nice if we clean up user submitted state to: START, STOP, FLEX, UPGRADE.
 ServiceClient change it to STARTING, STOPPING, FLEXING, UPGRADING.  After action is completed,
change it to STABLE.  We keep STOPPED, and STARTED keyword for backward compatibility.  Sorry,
this part was messed up during the original implementation.  Can you show example of JSON
that is used to trigger REST API upgrade?  I am getting error 500, and no errors in the log
file.  I am unsure what is wrong in my test samples.  It would be nice to see a working example.

> Yarn Service Upgrade: add support to upgrade a component instance 
> ------------------------------------------------------------------
>                 Key: YARN-7939
>                 URL: https://issues.apache.org/jira/browse/YARN-7939
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Chandni Singh
>            Assignee: Chandni Singh
>            Priority: Major
>         Attachments: YARN-7939.001.patch
> Yarn core supports in-place upgrade of containers. A yarn service can leverage that to
provide in-place upgrade of component instances. Please see YARN-7512 for details.
> Will add support to upgrade a single component instance first and then iteratively add other
APIs and features.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org

View raw message