[
https://issues.apache.org/jira/browse/HDFS-9847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lin Yiqun updated HDFS-9847:
----------------------------
Status: Patch Available (was: Open)
Attach a initial patch, thanks reviewing, the first updating configuration is
following:
* dfs.blockreport.initialDelay
* dfs.datanode.directoryscan.interval
* dfs.heartbeat.interval
* dfs.namenode.decommission.interval
* dfs.namenode.replication.interval
* dfs.namenode.checkpoint.period
* dfs.namenode.checkpoint.check.period
* dfs.client.datanode-restart.timeout
* dfs.ha.log-roll.period
* dfs.ha.tail-edits.period
* dfs.datanode.bp-ready.timeout
You can supply new configurations if you think I am missing some in this patch.
> HDFS configuration without time unit name should accept friendly time units
> ---------------------------------------------------------------------------
>
> Key: HDFS-9847
> URL: https://issues.apache.org/jira/browse/HDFS-9847
> Project: Hadoop HDFS
> Issue Type: Bug
> Affects Versions: 2.7.1
> Reporter: Lin Yiqun
> Assignee: Lin Yiqun
> Attachments: HDFS-9847.001.patch
>
>
> In HDFS-9821, it talks about the issue of leting existing keys use friendly
> units e.g. 60s, 5m, 1d, 6w etc. But there are som configuration key names
> contain time unit name, like {{dfs.blockreport.intervalMsec}}, so we can make
> some other configurations which without time unit name to accept friendly
> time units. The time unit {{seconds}} is frequently used in hdfs. We can
> updating this configurations first.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
