[jira] [Commented] (TEZ-4109) Improve TezCommonUtils.getCredentialsInfo and use it from more contexts

["László Bodor (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/TEZ-4109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17038142#comment-17038142 ] 

László Bodor commented on TEZ-4109:
-----------------------------------

pushed to master, thanks [~ashutoshc] for the review

> Improve TezCommonUtils.getCredentialsInfo and use it from more contexts
> -----------------------------------------------------------------------
>
>                 Key: TEZ-4109
>                 URL: https://issues.apache.org/jira/browse/TEZ-4109
>             Project: Apache Tez
>          Issue Type: Improvement
>            Reporter: László Bodor
>            Assignee: László Bodor
>            Priority: Major
>         Attachments: TEZ-4109.01.patch, TEZ-4109.02.patch, TEZ-4109.03.patch
>
>
> While debugging token related issues, I found the current implementation of TezCommonUtils.getCredentialsInfo doesn't provide enough info about tokens.
> 1. as it's used on DEBUG level (called from logCredentials, which has a debugenabled check), it should give more verbose output
> currently it's
> {code}
> token.getService()).append("(").append(token.getKind()).append(")")
> {code}
> but in case of delegation token issue, we would need to see token's full string representation, like this below:
> {code}
> Kind: HDFS_DELEGATION_TOKEN, Service: 10.14.67.148:8020, Ident: (token for hive: HDFS_DELEGATION_TOKEN owner=hive/dev-lbodor-hiveontez-sec-3.domain.com@REALM, renewer=yarn, realUser=, issueDate=1573566780144, maxDate=1574171580144, sequenceNumber=7611, masterKeyId=3)
> {code}
> 2. It should be called from more code paths (e.g. from within tasks), so it's going to let us follow tokens for every level of execution (AM, Container, Task)



--
This message was sent by Atlassian Jira
(v8.3.4#803005)