[
https://issues.apache.org/jira/browse/HADOOP-10483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14232806#comment-14232806
]
Vinayakumar B commented on HADOOP-10483:
----------------------------------------
Hi Alec,
I checked {{DurationFormatUtils.formatDurationHMS}} output.
Its not actually printing as you mentioned in description as "0d:1h:3m:2s:3ms".
It just prints "01:03:02:003".
In general, {{tokenRemoverScanInterval}} not expected to have values less than
1 min, though no strict validation is present.
> 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
> Attachments: HADOOP-10483.patch
>
>
> 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.3.4#6332)
