hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Zhijie Shen (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-514) Delayed store operations should not result in RM unavailability for app submission
Date Wed, 10 Apr 2013 04:48:16 GMT

     [ 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.1.patch

In this patch, I've changed RMStateStore#storeApplication from blocking API to non-blocking
API. Therefore, it is no longer necessary to invoke the API in ClientRMService#submitApplication.
Instead, I defined a new state, named SAVING, between NEW and SUBMITTED of RMApp. TestRMAppTransitions
were modified to test the additional state transition, and to test whether the application
is stored before SUBMITTED and removed after FINISHED.

An additional issue is that the mapping between yarn and mapreduce states needs to be updated
due to the newly added state. This will be filed and solved in a separate MR jira.
                
> 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
>
>
> 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

Mime
View raw message