[
https://issues.apache.org/jira/browse/HDFS-11140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15666311#comment-15666311
]
Xiaoyu Yao commented on HDFS-11140:
-----------------------------------
Thanks [~xiaochen] for reporting the issue and [~linyiqun] for posting the
patch.
How about removing the starting timestamp as the log4j always has that info at
the beginning of each log entry? This way we don't need to add logic to covert
the epoch and unit test for it.
{code}
INFO org.apache.hadoop.hdfs.server.datanode.DirectoryScanner: Periodic
Directory Tree Verification scan starting with interval of 21600000ms
{code}
> Directory Scanner should log startup message time correctly
> -----------------------------------------------------------
>
> Key: HDFS-11140
> URL: https://issues.apache.org/jira/browse/HDFS-11140
> Project: Hadoop HDFS
> Issue Type: Bug
> Affects Versions: 2.7.1
> Reporter: Xiao Chen
> Assignee: Yiqun Lin
> Priority: Trivial
> Labels: newbie
> Attachments: HDFS-11140.001.patch
>
>
> When DirectoryScanner is enabled, one can see the following log:
> {noformat}
> INFO org.apache.hadoop.hdfs.server.datanode.DirectoryScanner: Periodic
> Directory Tree Verification scan starting at 1479189895562ms with interval of
> 21600000ms
> {noformat}
> The first is epoch time and should not have 'ms'. Or better yet, we can
> change it to a human-readable format.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
