You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "hemanthboyina (Jira)" <ji...@apache.org> on 2019/09/01 08:50:00 UTC
[jira] [Updated] (HDFS-14630) Configuration.getTimeDurationHelper()
should not log time unit warning in info log.
[ https://issues.apache.org/jira/browse/HDFS-14630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
hemanthboyina updated HDFS-14630:
---------------------------------
Attachment: HDFS-14630.001.patch
> Configuration.getTimeDurationHelper() should not log time unit warning in info log.
> -----------------------------------------------------------------------------------
>
> Key: HDFS-14630
> URL: https://issues.apache.org/jira/browse/HDFS-14630
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: hdfs
> Affects Versions: 3.1.1
> Reporter: Surendra Singh Lilhore
> Assignee: hemanthboyina
> Priority: Minor
> Attachments: HDFS-14630.001.patch, HDFS-14630.patch
>
>
> To solve [HDFS-12920|https://issues.apache.org/jira/browse/HDFS-12920] issue we configured "dfs.client.datanode-restart.timeout" without time unit. No log file is full of
> {noformat}
> 2019-06-22 20:13:14,605 | INFO | pool-12-thread-1 | No unit for dfs.client.datanode-restart.timeout(30) assuming SECONDS org.apache.hadoop.conf.Configuration.logDeprecation(Configuration.java:1409){noformat}
> No need to log this, just give the behavior in property description.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org