[
https://issues.apache.org/jira/browse/HDFS-9821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15159391#comment-15159391
]
Steve Loughran commented on HDFS-9821:
--------------------------------------
Commented. Before dismissing millis, while they are useless for specifying
things like a weekly backup rate, they are very useful for setting delays
between operations in tests. If you have a chain of async processes all with a
minimum delay of 1s in buffered writes, async reads, async refreshes, then you
are looking at 5+s delay across the different threads, which slows tests down
significantly. Hence: it should be a valid parameter, and code should ask for a
time in millis, expecting Configuration to expand things
> HDFS configuration should accept friendly time units
> ----------------------------------------------------
>
> Key: HDFS-9821
> URL: https://issues.apache.org/jira/browse/HDFS-9821
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: datanode, namenode
> Affects Versions: 2.8.0
> Reporter: Arpit Agarwal
> Assignee: Xiaobing Zhou
>
> HDFS configuration keys that define time intervals use units inconsistently
> (Hours, seconds, milliseconds).
> Not all keys have the unit as part of their name. Related keys may use
> different units e.g. {{dfs.blockreport.intervalMsec}} accepts msec while
> {{dfs.blockreport.initialDelay}} accepts seconds. Milliseconds is rarely
> useful as a time unit which makes these values hard to parse when reading
> config files.
> We can either
> # Let existing keys use friendly units e.g. 60s, 5m, 1d, 6w etc. This can be
> done compatibly since there will be no conflict with existing valid
> configuration.
> # Just deprecate the existing keys and define new ones that accept friendly
> units.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
