hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jian He (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-674) Slow or failing DelegationToken renewals on submission itself make RM unavailable
Date Wed, 06 Nov 2013 00:32:18 GMT

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

Jian He commented on YARN-674:

Saw this is changed back to asynchronous submission on recovery, the original intention was
to prevent client from seeing the application as a new application. If asynchronously, the
client can query the application before recover event gets processed, meaning before the application
is fully recovered as some recover logic happens when app is processing the recover event(app.FinalTransition).

     // Recover the app synchronously, as otherwise client is possible to see
      // the application not recovered before it is actually recovered because
      // ClientRMService is already started at this point of time.
      appImpl.handle(new RMAppEvent(appImpl.getApplicationId(),

> Slow or failing DelegationToken renewals on submission itself make RM unavailable
> ---------------------------------------------------------------------------------
>                 Key: YARN-674
>                 URL: https://issues.apache.org/jira/browse/YARN-674
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: resourcemanager
>            Reporter: Vinod Kumar Vavilapalli
>            Assignee: Omkar Vinit Joshi
>         Attachments: YARN-674.1.patch, YARN-674.2.patch, YARN-674.3.patch, YARN-674.4.patch,
YARN-674.5.patch, YARN-674.5.patch
> This was caused by YARN-280. A slow or a down NameNode for will make it look like RM
is unavailable as it may run out of RPC handlers due to blocked client submissions.

This message was sent by Atlassian JIRA

View raw message