[
https://issues.apache.org/jira/browse/HADOOP-13582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xiao Chen updated HADOOP-13582:
-------------------------------
Resolution: Invalid
Status: Resolved (was: Patch Available)
Oops... on a closer look we do log the details in the next call,
{{removeStoredToken}}. Sorry for the churn... closing this as invalid.
SequenceNumber should be enough to ID a token, and the other info can be found
in the logs when searching for that ID, so I think it's fine. Thanks for the
suggestion Wei-Chiu!
> Implement logExpireToken in ZKDelegationTokenSecretManager
> ----------------------------------------------------------
>
> Key: HADOOP-13582
> URL: https://issues.apache.org/jira/browse/HADOOP-13582
> Project: Hadoop Common
> Issue Type: Improvement
> Components: kms
> Affects Versions: 2.8.0
> Reporter: Xiao Chen
> Assignee: Xiao Chen
> Priority: Minor
> Labels: supportability
> Attachments: HADOOP-13582.01.patch
>
>
> During my investigation on HADOOP-13487, I found it pretty difficult to track
> KMS DTs in ZK, even in debug level.
> Adding a simple debug log to make future triages easier.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
