t; -Ben
>
> -Original Message-
> From: alo.alt [mailto:wget.n...@googlemail.com]
> Sent: Friday, January 06, 2012 12:45 PM
> To: hdfs-user@hadoop.apache.org
> Subject: Re: HDFS load balancing for non-local reads
>
> Ben,
>
> the scenario should not happen, if one DN has
e-
From: alo.alt [mailto:wget.n...@googlemail.com]
Sent: Friday, January 06, 2012 12:45 PM
To: hdfs-user@hadoop.apache.org
Subject: Re: HDFS load balancing for non-local reads
Ben,
the scenario should not happen, if one DN has 20 clients and the other zero
(same block) the cluster (or DN) has another pro
05, 2012 5:33 PM
> To: hdfs-user@hadoop.apache.org
> Subject: Re: HDFS load balancing for non-local reads
>
> Currently it sorts the block locations as:
> # local node
> # local rack node
> # random order of remote nodes
>
> See DatanodeManager#sortLocatedBlock(...) and
&g
ode B is serving 1 client, they both have a 50%
chance of being selected for the 21st client?
-Ben
From: Suresh Srinivas [mailto:sur...@hortonworks.com]
Sent: Thursday, January 05, 2012 5:33 PM
To: hdfs-user@hadoop.apache.org
Subject: Re: HDFS load balancing for non-local reads
Current
Currently it sorts the block locations as:
# local node
# local rack node
# random order of remote nodes
See DatanodeManager#sortLocatedBlock(...) and
NetworkTopology#pseudoSortByDistance(...).
You can play around with other policies by plugging in different
NetworkTopology.
On Thu, Jan 5, 2012
Hi-
How does the NameNode handle load balancing of non-local reads with multiple
block locations when locality is equal?
IE, if the client is equidistant (same rack) from 2 DataNodes hosting the
same block, does the NameNode consider current client count or any other
load indicators when de
