[
https://issues.apache.org/jira/browse/YARN-5932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15708785#comment-15708785
]
Sunil G commented on YARN-5932:
-------------------------------
Thanks [~rohithsharma].
As discussed, there are some similar changes done in FairScheduler too.
A quick summary of changes.
1. Introduced {{preValidateMoveApplication}} api to validate whether move
operation can be successful or not. Few code is taken out from
FS#moveApplication for same.
2. By using above api, we are trying to achieve a similar behavior for all app
update changes from cli/rest etc.
[~kasha], could you please help to take a look.
[~rohithsharma], please help to add any points if I missed some. Thank you.
> 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]
