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

MENG DING updated YARN-4175:
----------------------------
    Attachment: YARN-4175.2.patch

Update the example program as client APIs have been changed in YARN-1509 and 
YARN-1510. Now the client program does not need to distinguish between Increase 
or Decrease action, it just needs to pass in the container ID, and the target 
resource capability.

How to use the example program:
* To enable IPC service in the application master, user needs to specify the 
*enable_ipc* option. For example:
{code}hadoop org.apache.hadoop.yarn.applications.distributedshell.Client -jar 
/usr/local/hadoop/share/hadoop/yarn/hadoop-yarn-applications-distributedshell-3.0.0.jar
 -shell_command "sleep 100000" -num_containers 10 -enable_ipc{code}
* Once the application has started, user can start a *new* client and specify 
the *appmaster* option to set the client to the appmaster mode. Under this 
mode, the client will talk directly with appmaster, and user can specify 
*application_id*, *container_id*, *action*, *container_memory*, 
*container_vcores* options to request container resizing. For example, to 
change a container resource, the user can do:
{code}hadoop org.apache.hadoop.yarn.applications.distributedshell.Client 
-appmaster -application_id=<app_id> -container_id=<container_id> 
-action=CHANGE_CONTAINER -container_memory=2048 -container_vcores=1{code}

> Example of use YARN-1197
> ------------------------
>
>                 Key: YARN-4175
>                 URL: https://issues.apache.org/jira/browse/YARN-4175
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: api, nodemanager, resourcemanager
>            Reporter: Wangda Tan
>            Assignee: MENG DING
>         Attachments: YARN-4175.1.patch, YARN-4175.2.patch
>
>
> Like YARN-2609, we need a example program to demonstrate how to use YARN-1197 
> from end-to-end.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to