[
https://issues.apache.org/jira/browse/YARN-2147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14034612#comment-14034612
]
Daryn Sharp commented on YARN-2147:
-----------------------------------
I don't think the patch handles the use case it's designed for. If job
submission failed with a bland "Read timed out", then logging all the tokens in
the RM log doesn't help the end user, nor does the RM log even answer the
question "which token timed out"?
What you really want to do is change
{{DelegationTokenRenewer#handleAppSubmitEvent}} to trap exceptions from
{{renewToken}}. Wrap the exception with a more descriptive exception that
stringifies to the user as "Can't renew token <blah>: Read timed out".
> client lacks delegation token exception details when application submit fails
> -----------------------------------------------------------------------------
>
> Key: YARN-2147
> URL: https://issues.apache.org/jira/browse/YARN-2147
> Project: Hadoop YARN
> Issue Type: Bug
> Components: resourcemanager
> Affects Versions: 2.4.0
> Reporter: Jason Lowe
> Assignee: Chen He
> Priority: Minor
> Attachments: YARN-2147-v2.patch, YARN-2147.patch
>
>
> When an client submits an application and the delegation token process fails
> the client can lack critical details needed to understand the nature of the
> error. Only the message of the error exception is conveyed to the client,
> which sometimes isn't enough to debug.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
