hadoop-yarn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinod Kumar Vavilapalli (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (YARN-514) Delayed store operations should not result in RM unavailability for app submission
Date Thu, 18 Apr 2013 17:52:14 GMT

     [ https://issues.apache.org/jira/browse/YARN-514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Vinod Kumar Vavilapalli resolved YARN-514.
------------------------------------------

       Resolution: Fixed
    Fix Version/s: 2.0.5-beta
     Hadoop Flags: Reviewed

I checked in YARN-585 to trunk and branch-2. Closing this as resolved.
                
> 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
>             Fix For: 2.0.5-beta
>
>         Attachments: YARN-514.1.patch, YARN-514.2.patch, YARN-514.3.patch, YARN-514.4.patch,
YARN-514.5.patch, YARN-514.6.patch, YARN-514.7.patch, YARN-514.8.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