hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Omkar Vinit Joshi (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-674) Slow or failing DelegationToken renewals on submission itself make RM unavailable
Date Tue, 29 Oct 2013 00:08:32 GMT

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

Omkar Vinit Joshi commented on YARN-674:

Thanks [~zjshen] and [~jianhe] for reviewing..

bq. DelegationTokenRenewer.applicationFinished() is anyways canceling the token on a separate
thread, do we need to funnel through the dispatcher as well ?
discussed with [~jianhe] offline.. We need this because user may just submit an application
and kill it immediately after it. The earlier submitted application may still be in flight
(in dispatcher queue) and we may try to process application finish event as a part of kill
before it. To avoid this I am enqueuing it.

bq. It would be to have an end-to-end test that application submitted with an Invalid token
will be rejected and verify yarn client can get Failed application status using MockRM.
Added the test

> 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
> 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