hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bikas Saha (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-514) Delayed store operations should not result in RM unavailability for app submission
Date Fri, 12 Apr 2013 03:47:16 GMT

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

Bikas Saha commented on YARN-514:
---------------------------------

For MAPREDUCE-5140 please check for uses of both NEW and SUBMITTED in order to find out places
where NEW_SAVING would need to be handled.
                
> 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

Mime
View raw message