[
https://issues.apache.org/jira/browse/YARN-514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhijie Shen updated YARN-514:
-----------------------------
Attachment: YARN-514.3.patch
I've updated the patch. the major modifications are as follows:
1. SAVING is renamed as NEW_SAVING to be more clear.
2. On receiving RMAppEventType.START, RMApp transits from NEW to NEW_SAVING,
and RMAppSavingTransition is executed, where storeApplication is invoked. On
receiving RMAppEventType.APP_SAVED (sent from RMStateStore), RMApp transits
from NEW_SAVING to SUBMITTED, and StartAppAttemptTransition is executed, where
application store exception is checked before creating a new attempt.
Therefore, the states of RMApp from SUBMITTED are just moved a step behind
without any more changes.
3. TestRMAppTransitions has been significantly simplified. Only the transition
related tests for the newly added state is included here.
In addition, I've done the single-node cluster test, and verified that
application store occurs before attempt store.
> Delayed store operations should not result in RM unavailability for app
> submission
> ----------------------------------------------------------------------------------
>
> Key: YARN-514
> URL: https://issues.apache.org/jira/browse/YARN-514
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: resourcemanager
> Reporter: Bikas Saha
> Assignee: Zhijie Shen
> Attachments: YARN-514.1.patch, YARN-514.2.patch, YARN-514.3.patch
>
>
> Currently, app submission is the only store operation performed synchronously
> because the app must be stored before the request returns with success. This
> makes the RM susceptible to blocking all client threads on slow store
> operations, resulting in RM being perceived as unavailable by clients.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
