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 "Jian He (JIRA)" <ji...@apache.org> on 2016/05/27 21:31:13 UTC
[jira] [Updated] (YARN-5175) Simplify the delegation token renewal
management for YARN localization and log-aggregation
[ https://issues.apache.org/jira/browse/YARN-5175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jian He updated YARN-5175:
--------------------------
Description:
Increasingly, this DelegationTokenRenewer class for renewing expiring token for localization and log-aggregation is getting complicated. We could have done it at a per-user level. copying comments from vinod in YARN-5098:
bq. Overall, I think we can simplify this code if we simply always manage our own tokens for localization and log-aggregation for long-running applications / services. Today, it's too complicated: for the first day, we use the user's token T, second day we get a new token T' but share it for all the apps originally sharing T, after RM restart we use a new token T'' which is different for each of the apps originally sharing T. We can simplify this by always managing it ourselves and managing them per-user!
was:Increasingly, this DelegationTokenRenewer class for renewing expiring token for localization and log-aggregation is getting complicated. We could have done it at a per-user level. copying comments from vinod in YARN-5098
> Simplify the delegation token renewal management for YARN localization and log-aggregation
> ------------------------------------------------------------------------------------------
>
> Key: YARN-5175
> URL: https://issues.apache.org/jira/browse/YARN-5175
> Project: Hadoop YARN
> Issue Type: Bug
> Reporter: Jian He
>
> Increasingly, this DelegationTokenRenewer class for renewing expiring token for localization and log-aggregation is getting complicated. We could have done it at a per-user level. copying comments from vinod in YARN-5098:
> bq. Overall, I think we can simplify this code if we simply always manage our own tokens for localization and log-aggregation for long-running applications / services. Today, it's too complicated: for the first day, we use the user's token T, second day we get a new token T' but share it for all the apps originally sharing T, after RM restart we use a new token T'' which is different for each of the apps originally sharing T. We can simplify this by always managing it ourselves and managing them per-user!
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org