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 Fri, 25 Oct 2013 00:19:02 GMT

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

Omkar Vinit Joshi commented on YARN-674:

updating the patch
Modifying the event flow
* In unsecured case nothing will change
* In secured case
** For Recovery
*** ApplicationEvents will be enqueued when we are recovering. When service starts they will
get processed.
** For normal app submission
*** Event will be enqueued into the separate DelegationTokenRenewer dispatcher queue and client's
request will be returned immediately.
*** If the token renewal is successful then renewer will send the START/RECOVER event else
it will fail the app.

* Testing
** Updated unit test to test the updated behavior
** Manually tested it on secured cluster
*** tested app submission with by default HDFS TOKEN and it works.
*** tested same by restarting RM in between

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