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 "Alec Ten Harmsel (JIRA)" <ji...@apache.org> on 2014/11/26 16:38:13 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 ]

Alec Ten Harmsel updated HADOOP-10483:
--------------------------------------
    Attachment: HADOOP-10483.patch

Please review patch. It's a very simple change, just wrapping a duration in milliseconds in a call to DurationFormatUtils.formatDurationHMS() instead of doing the math manually.

> 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)