You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@hadoop.apache.org by ch huang <ju...@gmail.com> on 2014/05/29 11:19:51 UTC
question about balance info
hi,maillist:
when i do balance cluster , i see the following information ,i am
very confused, why the block moved from 192.168.10.36 to 192.168.10.14 ,it
should through 192.168.10.34?
INFO balancer.Balancer: Moving block -1259523420126578490 from
192.168.10.36:50011 to 192.168.10.14:50011 through 192.168.10.34:50011 is
succeeded
Re: question about balance info
Posted by Binglin Chang <de...@gmail.com>.
there are multiple replicas for a block, we don't need to move a block from
source -> dest, just find a node with the block, and copy it to dest, then
delete replica on the source. Why? We can choose a node which is closest to
dest, or the source node is busy(too many blocks to move), make sense?
On Thu, May 29, 2014 at 5:19 PM, ch huang <ju...@gmail.com> wrote:
> hi,maillist:
> when i do balance cluster , i see the following information ,i am
> very confused, why the block moved from 192.168.10.36 to 192.168.10.14 ,it
> should through 192.168.10.34?
>
> INFO balancer.Balancer: Moving block -1259523420126578490 from
> 192.168.10.36:50011 to 192.168.10.14:50011 through 192.168.10.34:50011 is
> succeeded
>
Re: question about balance info
Posted by Binglin Chang <de...@gmail.com>.
there are multiple replicas for a block, we don't need to move a block from
source -> dest, just find a node with the block, and copy it to dest, then
delete replica on the source. Why? We can choose a node which is closest to
dest, or the source node is busy(too many blocks to move), make sense?
On Thu, May 29, 2014 at 5:19 PM, ch huang <ju...@gmail.com> wrote:
> hi,maillist:
> when i do balance cluster , i see the following information ,i am
> very confused, why the block moved from 192.168.10.36 to 192.168.10.14 ,it
> should through 192.168.10.34?
>
> INFO balancer.Balancer: Moving block -1259523420126578490 from
> 192.168.10.36:50011 to 192.168.10.14:50011 through 192.168.10.34:50011 is
> succeeded
>
Re: question about balance info
Posted by Binglin Chang <de...@gmail.com>.
there are multiple replicas for a block, we don't need to move a block from
source -> dest, just find a node with the block, and copy it to dest, then
delete replica on the source. Why? We can choose a node which is closest to
dest, or the source node is busy(too many blocks to move), make sense?
On Thu, May 29, 2014 at 5:19 PM, ch huang <ju...@gmail.com> wrote:
> hi,maillist:
> when i do balance cluster , i see the following information ,i am
> very confused, why the block moved from 192.168.10.36 to 192.168.10.14 ,it
> should through 192.168.10.34?
>
> INFO balancer.Balancer: Moving block -1259523420126578490 from
> 192.168.10.36:50011 to 192.168.10.14:50011 through 192.168.10.34:50011 is
> succeeded
>
Re: question about balance info
Posted by Binglin Chang <de...@gmail.com>.
there are multiple replicas for a block, we don't need to move a block from
source -> dest, just find a node with the block, and copy it to dest, then
delete replica on the source. Why? We can choose a node which is closest to
dest, or the source node is busy(too many blocks to move), make sense?
On Thu, May 29, 2014 at 5:19 PM, ch huang <ju...@gmail.com> wrote:
> hi,maillist:
> when i do balance cluster , i see the following information ,i am
> very confused, why the block moved from 192.168.10.36 to 192.168.10.14 ,it
> should through 192.168.10.34?
>
> INFO balancer.Balancer: Moving block -1259523420126578490 from
> 192.168.10.36:50011 to 192.168.10.14:50011 through 192.168.10.34:50011 is
> succeeded
>