[
https://issues.apache.org/jira/browse/HDFS-5215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14728240#comment-14728240
]
Chris Nauroth commented on HDFS-5215:
-------------------------------------
It appears this patch had a side effect of counting
{{dfs.datanode.du.reserved}} space towards non-DFS used as reported by {{hdfs
dfsadmin -report}}. Prior to this patch, reserved space did not count towards
non-DFS used. Was this intentional, or was it an unintended side effect? My
opinion is that the definition of non-DFS used should not have changed. Please
let me know your thoughts, and if necessary, we can file a new follow-up jira.
> dfs.datanode.du.reserved is not considered while computing available space
> --------------------------------------------------------------------------
>
> Key: HDFS-5215
> URL: https://issues.apache.org/jira/browse/HDFS-5215
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: datanode
> Affects Versions: 3.0.0, 2.7.0
> Reporter: Brahma Reddy Battula
> Assignee: Brahma Reddy Battula
> Fix For: 2.7.1
>
> Attachments: HDFS-5215-002.patch, HDFS-5215-003.patch,
> HDFS-5215-004.patch, HDFS-5215-005.patch, HDFS-5215.patch
>
>
> {code}public long getAvailable() throws IOException {
> long remaining = getCapacity()-getDfsUsed();
> long available = usage.getAvailable();
> if (remaining > available) {
> remaining = available;
> }
> return (remaining > 0) ? remaining : 0;
> }
> {code}
> Here we are not considering the reserved space while getting the Available
> Space.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
