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

Yufei Gu commented on YARN-6001:
--------------------------------

Make sense to me. Thanks to point out.
It would be swell to be explicit about the direction, like "changetoqueue", 
“migratetoqueue”. It is obvious for the people who actually write the command 
to move app that the parameter queue should be the target queue instead of 
source queue, but may confuse some admins or support guys who maintain system 
with pre-baked scripts.

> Improve moveApplicationQueues command line
> ------------------------------------------
>
>                 Key: YARN-6001
>                 URL: https://issues.apache.org/jira/browse/YARN-6001
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: client
>            Reporter: Sunil G
>            Assignee: Sunil G
>         Attachments: YARN-6001.0001.patch
>
>
> As an example, below command is used to move an application across queue. 
> {noformat}./yarn application -movetoqueue  application_1479894790219_0002 
> -queue default{noformat}
> Inline  with other application's attribute modification features such as 
> updateTimeout or priority, movetoqueue cli command lacks unification and more 
> complex or error prone.
> Suggesting below cli command which can be used.
> {noformat}
> ./yarn application -appId application_1479894790219_0002 -move default
> {noformat}
> This is inline with other commands such as 
> {noformat}
> ./yarn application -appId  application_1479894790219_0002 -updatePriority 8 
> ./yarn application -appId  application_1479894790219_0002 -updateLifetime 10
> {noformat}
> Old *movetoqueue* command could be still kept, but we can mark it as 
> deprecated and mention in help message.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to