Namenode doesn't accurately know datanodes free-space

2013-10-29 Thread alex bohr 
I see that the Namenode always reports datanodes as having about 5% more
space then they actually do.

And I recently added some smaller datanodes into the cluster and the drives
filled up to 100%, not respecting the 5GB I had reserved for Map Reduce
with this property from mapred-site.xml:

  dfs.datanode.du.reserved
  5368709120


Has anyone else experienced this behavior?

RE: Namenode doesn't accurately know datanodes free-space

2013-10-30 Thread Brahma Reddy Battula 
Dear Alex


"""Has anyone else experienced this behavior?""""

Yes, I had also experienced and raised jira for same..


Please have look on following issue..

https://issues.apache.org/jira/browse/HDFS-5215




From: alex bohr [alexjb...@gmail.com]
Sent: Wednesday, October 30, 2013 1:07 AM
To: user@hadoop.apache.org
Subject: Namenode doesn't accurately know datanodes free-space

I see that the Namenode always reports datanodes as having about 5% more space 
then they actually do.

And I recently added some smaller datanodes into the cluster and the drives 
filled up to 100%, not respecting the 5GB I had reserved for Map Reduce with 
this property from mapred-site.xml:

  dfs.datanode.du.reserved
  5368709120


Has anyone else experienced this behavior?