You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Wangda Tan (JIRA)" <ji...@apache.org> on 2014/04/09 04:19:14 UTC
[jira] [Updated] (HADOOP-10483)
AbstractDelegationTokenSecretManager.ExpiredTokenRemover should use
adaptable unit to print time
[ https://issues.apache.org/jira/browse/HADOOP-10483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Wangda Tan updated HADOOP-10483:
--------------------------------
Description: Currently, ExpiredTokenRemover uses minute(s) as unit to print tokenRemoverScanInterval. If user entered a value less than 1 min, it will become 0 in output log. It's better to use format like 0d:1h:3m:2s:3ms to print time. (was: Currently, ExpiredTokenRemover uses minute(s) as unit to print tokenRemoverScanInterval, it's possible that user entered a value less than 1 min. It will become 0 in output log. It's better to use format like 0d:1h:3m:2s:3ms to print time.)
> AbstractDelegationTokenSecretManager.ExpiredTokenRemover should use adaptable unit to print time
> ------------------------------------------------------------------------------------------------
>
> Key: HADOOP-10483
> URL: https://issues.apache.org/jira/browse/HADOOP-10483
> Project: Hadoop Common
> Issue Type: Bug
> Affects Versions: 2.4.0
> Reporter: Wangda Tan
> Priority: Trivial
>
> Currently, ExpiredTokenRemover uses minute(s) as unit to print tokenRemoverScanInterval. If user entered a value less than 1 min, it will become 0 in output log. It's better to use format like 0d:1h:3m:2s:3ms to print time.
--
This message was sent by Atlassian JIRA
(v6.2#6252)