[
https://issues.apache.org/jira/browse/HDFS-5215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13961795#comment-13961795
]
Brahma Reddy Battula commented on HDFS-5215:
--------------------------------------------
Hi [~fahlke],
Thanks for taking look into this issue..
{quote}
Have you considered that the underlying filesystem reserved space (ext3, ext4
-> tune2fs) can also affect this behavior?
{quote}
Yes, I checked in ext3 file system only..
{quote}
I'm not sure if this is a problem in hadoop-3.0.x anymore.
{quote}
As I knew , it is not fixed..problem will be present in hadoop-3.0.x . .Please
let me know your thoughts on this...
> dfs.datanode.du.reserved is not taking effect as it's not considered while
> getting the 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
> Reporter: Brahma Reddy Battula
> Assignee: Brahma Reddy Battula
> Fix For: 3.0.0
>
> Attachments: 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.2#6252)
