You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "chaosju (Jira)" <ji...@apache.org> on 2022/05/16 14:25:00 UTC
[jira] [Assigned] (YARN-11112) Avoid renewing delegation token when app is first submitted to RM
[ https://issues.apache.org/jira/browse/YARN-11112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
chaosju reassigned YARN-11112:
------------------------------
Assignee: Yuanbo Liu
> Avoid renewing delegation token when app is first submitted to RM
> -----------------------------------------------------------------
>
> Key: YARN-11112
> URL: https://issues.apache.org/jira/browse/YARN-11112
> Project: Hadoop YARN
> Issue Type: Improvement
> Reporter: Yuanbo Liu
> Assignee: Yuanbo Liu
> Priority: Major
> Labels: pull-request-available
> Attachments: image-2022-04-19-10-34-59-573.png, image-2022-04-19-10-38-01-194.png
>
> Time Spent: 2h 10m
> Remaining Estimate: 0h
>
> When auth is enabled by NameNode, then delegation token is required if application needs to acess files/directoies. We find that when app is first submitted to RM, RM renewer will renew app token no matter whether token is expired or not. Renewing token is a bit heavy since it uses global write lock. Here is the result when delegation token is required in a very busy cluster.
> !image-2022-04-19-10-34-59-573.png|width=515,height=302!
> !image-2022-04-19-10-38-01-194.png|width=490,height=290!
>
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org