Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Tue, 17 Oct 2017 22:19:00 +0000 (UTC)
From: "Eric Yang (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.13103348.1505852569000.21466.1508278740173@Atlassian.JIRA>
In-Reply-To: <JIRA.13103348.1505852569000@Atlassian.JIRA>
References: <JIRA.13103348.1505852569000@Atlassian.JIRA> <JIRA.13103348.1505852569420@jira-lw-us.apache.org>
Subject: [jira] [Updated] (YARN-7217) PUT method for update service for
 Service API doesn't function correctly
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 17 Oct 2017 22:19:05 -0000


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

Eric Yang updated YARN-7217:
----------------------------
    Attachment: YARN-7217.yarn-native-services.003.patch

The pre-commit test seems to use a previous build of hadoop-yarn-common to test with hadoop-yarn-services-core and hadoop-yarn-services-api.  The undefined symbol are changes in hadoop-yarn-common.  Findbugs reported error is also existing issue in hadoop-yarn-api project, and not related to the patch.  

> PUT method for update service for Service API doesn't function correctly
> ------------------------------------------------------------------------
>
>                 Key: YARN-7217
>                 URL: https://issues.apache.org/jira/browse/YARN-7217
>             Project: Hadoop YARN
>          Issue Type: Task
>          Components: api, applications
>            Reporter: Eric Yang
>            Assignee: Eric Yang
>         Attachments: YARN-7217.yarn-native-services.001.patch, YARN-7217.yarn-native-services.002.patch, YARN-7217.yarn-native-services.003.patch
>
>
> The PUT method for updateService API provides multiple functions:
> # Stopping a service.
> # Start a service.
> # Increase or decrease number of containers.
> The overloading is buggy depending on how the configuration should be applied.
> Scenario 1
> A user retrieves Service object from getService call, and the Service object contains state: STARTED.  The user would like to increase number of containers for the deployed service.  The JSON has been updated to increase container count.  The PUT method does not actually increase container count.
> Scenario 2
> A user retrieves Service object from getService call, and the Service object contains state: STOPPED.  The user would like to make a environment configuration change.  The configuration does not get updated after PUT method.
> This is possible to address by rearranging the logic of START/STOP after configuration update.  However, there are other potential combinations that can break PUT method.  For example, user like to make configuration changes, but not yet restart the service until a later time.
> The alternative is to separate the PUT method into PUT method for configuration vs status.  This increase the number of action that can be performed.  New API could look like:
> {code}
> @PUT
> /ws/v1/services/[service_name]/config
> Request Data:
> {
>   "name":"[service_name]",
>   "number_of_containers": 5
> }
> {code}
> {code}
> @PUT
> /ws/v1/services/[service_name]/state
> Request data:
> {
>   "name": "[service_name]",
>   "state": "STOPPED|STARTED"
> }
> {code}


--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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