[
https://issues.apache.org/jira/browse/YARN-5932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15697775#comment-15697775
]
Sunil G edited comment on YARN-5932 at 11/26/16 11:29 AM:
----------------------------------------------------------
Attaching v1 patch.
Changes:
- Introduced new command for move : {{yarn application -appId <app Id> -move
queueB}}. Old one is deprecated, but will still work.
- Removed RMAppMoveEvent handling. RMApp need not have to handle MOVE event as
we introduced new api in RMAppManager.
- Changed FairScheduler in align with new design approach.
cc/ [~rohithsharma] and [~jianhe]
was (Author: sunilg):
Attaching v1 patch.
Changes:
- Introduced new command for move : {{yarn application -appId <app Id> -move
queueB }}. Old one is deprecated, but will still work.
- Removed RMAppMoveEvent handling. RMApp need not have to handle MOVE event as
we introduced new api in RMAppManager.
- Changed FairScheduler in align with new design approach.
cc/ [~rohithsharma] and [~jianhe]
> Retrospect moveApplicationToQueue in align with YARN-5611
> ---------------------------------------------------------
>
> Key: YARN-5932
> URL: https://issues.apache.org/jira/browse/YARN-5932
> Project: Hadoop YARN
> Issue Type: Bug
> Components: capacity scheduler, resourcemanager
> Reporter: Sunil G
> Assignee: Sunil G
> Attachments: YARN-5932.v0.patch, YARN-5932.v1.patch
>
>
> All dynamic api's of an application's state change could follow a general
> design approach. Currently priority and app timeouts are following this
> approach all corner cases.
> *Steps*
> - Do a pre-validate check to ensure that changes are fine.
> - Update this information to state-store
> - Perform real move operation and update in-memory data structures.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
