hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alec Ten Harmsel (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-10483) AbstractDelegationTokenSecretManager.ExpiredTokenRemover should use adaptable unit to print time
Date Wed, 03 Dec 2014 23:01:13 GMT

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

Alec Ten Harmsel commented on HADOOP-10483:
-------------------------------------------

Hi Vinayakumar,

My bad, I can't believe I didn't check that. This output format makes sense to me, but I am
more than willing to write a patch that prints in the requested format. Which solution is
preferred?

Alec

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

Mime
View raw message