[HDFS-12698] Ozone: Use time units in the Ozone configuration values

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: HDFS-7240
• Component/s: ozone
• Hadoop Flags: Reviewed
• Assignee: Marton Elek
• Reporter: Marton Elek
• Created: 23/Oct/17 20:03
• Updated: 26/Apr/18 21:56
• Resolved: 18/Dec/17 21:08

Description

In HDFS-9847 introduced a new way to configure the time related configuration with using time unit in the vaule (eg. 10s, 5m, ...).

Because the new behavior I have seen a lot of warning during my tests:

2017-10-19 18:35:19,955 [main] INFO  Configuration.deprecation (Configuration.java:logDeprecation(1306)) - No unit for scm.container.client.idle.threshold(10000) assuming MILLISECONDS

So we need to add the time unit for every configuration. Unfortunately we have a few configuration parameter which includes the unit in the key name (eg dfs.cblock.block.buffer.flush.interval.seconds or ozone.container.report.interval.ms).

I suggest to remove all the units from the key name and follow the new convention where any of the units could be used.

Issue Links

• is duplicated by: HDFS-12785 Ozone: Add timeunit for ozone.scm.heartbeat.interval.seconds in ozone-default.xml