[
https://issues.apache.org/jira/browse/HDFS-12078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Weiwei Yang updated HDFS-12078:
-------------------------------
Description:
The description of property {{dfs.namenode.stale.datanode.interva}} in
hdfs-default.xml doesn't mention about the time unit, we should add that to
avoid confusing users.
I have reviewed all properties in hdfs-default.xml, this is the only one
property causes such confusion, user should be able to easily figure out the
appropriate time unit for properties by either
* Specified by property name, e.g dfs.namenode.full.block.report.lease.length.ms
* Specified by property value with time unit suffix, e.g
dfs.blockreport.initialDelay=0s
* Explained by description of the property, e.g
dfs.namenode.safemode.extension=3000, description: Determines extension of safe
mode in milliseconds ...
change to the property name and value will be an incompatible change, to
minimize the impact, propose to simply add the time unit in the description
(3rd approach). And this should be only one property needs the fix in
hdfs-default.xml.
was:
The description of property {{dfs.namenode.stale.datanode.interva}} in
hdfs-default.xml doesn't mention about the time unit, we should add that to
avoid confusing users.
I have reviewed all properties in hdfs-default.xml, this is the only one
property causes such confusion, user should be able to easily figure out the
appropriate time unit for properties by either
* Specified by property name, e.g dfs.namenode.full.block.report.lease.length.ms
* Specified by property value with time unit suffix, e.g
dfs.blockreport.initialDelay=0s
* Explained by description of the property, e.g
dfs.namenode.safemode.extension=3000, description: Determines extension of safe
mode in milliseconds ...
change to the property name and value will be an incompatible change, to
minimize the impact, propose to simply add the time unit in the description.
And this should be only one property needs the fix in hdfs-default.xml.
> Add time unit to the description of property
> dfs.namenode.stale.datanode.interval in hdfs-default.xml
> -----------------------------------------------------------------------------------------------------
>
> Key: HDFS-12078
> URL: https://issues.apache.org/jira/browse/HDFS-12078
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: hdfs
> Reporter: Weiwei Yang
> Assignee: Weiwei Yang
> Priority: Trivial
>
> The description of property {{dfs.namenode.stale.datanode.interva}} in
> hdfs-default.xml doesn't mention about the time unit, we should add that to
> avoid confusing users.
> I have reviewed all properties in hdfs-default.xml, this is the only one
> property causes such confusion, user should be able to easily figure out the
> appropriate time unit for properties by either
> * Specified by property name, e.g
> dfs.namenode.full.block.report.lease.length.ms
> * Specified by property value with time unit suffix, e.g
> dfs.blockreport.initialDelay=0s
> * Explained by description of the property, e.g
> dfs.namenode.safemode.extension=3000, description: Determines extension of
> safe mode in milliseconds ...
> change to the property name and value will be an incompatible change, to
> minimize the impact, propose to simply add the time unit in the description
> (3rd approach). And this should be only one property needs the fix in
> hdfs-default.xml.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
