onworks.com'
Subject: RE: [HDFS-9038] Non-Dfs used Calculation
Remainder mail...
--Brahma Reddy Battula
-Original Message-
From: Brahma Reddy Battula
Sent: 20 April 2016 18:58
To: hdfs-dev; Tsz Wo Sze
Cc: 'cnaur...@hortonworks.com'; 'vinayakum...@apache.org';
'
Remainder mail...
--Brahma Reddy Battula
-Original Message-
From: Brahma Reddy Battula
Sent: 20 April 2016 18:58
To: hdfs-dev; Tsz Wo Sze
Cc: 'cnaur...@hortonworks.com'; 'vinayakum...@apache.org';
'aagar...@hortonworks.com'
Subject: RE: [HDFS-9038] Non-D
icas.get();
--Brahma Reddy Battula
-Original Message-
From: Ravi Prakash [mailto:ravihad...@gmail.com]
Sent: 16 April 2016 09:40
To: hdfs-dev; Tsz Wo Sze
Subject: Re: [HDFS-9038] Non-Dfs used Calculation
I meant HDFS-9530 instead of HDFS-9038. We are seeing an issue where none of
the d
I meant HDFS-9530 instead of HDFS-9038. We are seeing an issue where none
of the datanodes are available for writes, and my suspicion is that
incorrect calculation of all these numbers is causing it.
On Fri, Apr 15, 2016 at 6:38 PM, Ravi Prakash wrote:
> Hi Nicholas!
>
> Could you please point o
Hi Nicholas!
Could you please point out exactly which place you are seeing this
{{available = usage.getAvailable() - reserved}} calculation? I'm sorry I'm
a bit confused because there are several places you could be talking about
( in the patch / in the unpatched NN code / in the unpatched DN code
available = usage.getAvailable() - reserved
It is incorrect to minus reserved from usage.getAvailable() above since the
reserved space, which is the space reserved for non-hdfs used, may already be
occupied by some non-hdfs files but not necessarily empty space.
In pre HDFS-5215 calculation, the
