[
https://issues.apache.org/jira/browse/HDFS-6493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14025504#comment-14025504
]
Andrew Wang commented on HDFS-6493:
-----------------------------------
I think we should keep the default value to disabled, but the property and this
value should be documented in hdfs-default.xml.
It'd also be nice (if not true already) to pretty print this value on NN
startup, e.g. "30 minutes" rather than "1800 seconds". It'd actually be nice
follow-on work to look for similarly unfriendly values in the logs and pretty
printing them. There are some time-related function in DFSUtil (e.g.
durationToString, datetoIso8601String), but feel free to write your own
functions too.
> Propose to change "dfs.namenode.startup.delay.block.deletion" to second
> instead of millisecond
> ----------------------------------------------------------------------------------------------
>
> Key: HDFS-6493
> URL: https://issues.apache.org/jira/browse/HDFS-6493
> Project: Hadoop HDFS
> Issue Type: Bug
> Reporter: Juan Yu
> Assignee: Juan Yu
> Priority: Trivial
>
> Based on the discussion in https://issues.apache.org/jira/browse/HDFS-6186,
> the delay will be at least 30 minutes or even hours. it's not very user
> friendly to use milliseconds when it's likely measured in hours.
> I suggest to make the following change
> 1. change the unit of this config to second
> 2. rename the config key from "dfs.namenode.startup.delay.block.deletion.ms"
> to "dfs.namenode.startup.delay.block.deletion.sec"
> 3. add the default value to hdfs-default.xml, what's the reasonable value, 30
> minutes, one hour?
--
This message was sent by Atlassian JIRA
(v6.2#6252)
