[
https://issues.apache.org/jira/browse/HDFS-9872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15171632#comment-15171632
]
Lin Yiqun commented on HDFS-9872:
---------------------------------
Attach a initial patch, I did a code review and found the 11 configurations
first, as follow:
* dfs.datanode.du.reserved
* dfs.namenode.fs-limits.max-component-length
* dfs.namenode.fs-limits.min-block-size
* dfs.namenode.resource.du.reserved
* dfs.image.transfer.bandwidthPerSec
* dfs.image.transfer-bootstrap-standby.bandwidthPerSec
* dfs.image.transfer.chunksize
* dfs.datanode.available-space-volume-choosing-policy.balanced-space-threshold
* dfs.client.cache.readahead
* dfs.datanode.max.locked.memory
* dfs.namenode.fs-limits.max-xattr-size
And these configurations are bytes-default and haven't size unit name in key
name, welcome review.
> HDFS bytes-default configurations should accept multiply size units
> -------------------------------------------------------------------
>
> Key: HDFS-9872
> URL: https://issues.apache.org/jira/browse/HDFS-9872
> Project: Hadoop HDFS
> Issue Type: Bug
> Affects Versions: 2.7.1
> Reporter: Lin Yiqun
> Assignee: Lin Yiqun
> Attachments: HDFS-9872.001.patch
>
>
> In HDFS-1314 and HDFS-9842, it had make some configurations can be friendly
> accept multiply size unit, such as 134217728 can be also 128m, or 8048, can
> be also replaced by 8k. And in some configurations, the value will be large,
> like in
> {{dfs.datanode.available-space-volume-choosing-policy.balanced-space-threshold}},
> its default value is 10g, equal to 10737418240. Obviously, it's not
> convenient to direct transform. So we could make some hdfs bytes-default
> configurations which without size unit name be friendly accepted multiply
> size unit.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
