You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@hbase.apache.org by Jean-Daniel Cryans <jd...@apache.org> on 2011/03/21 21:50:29 UTC
Re: some regions can't be assigned
So you are testing a case where the master ends up being alone? I'm
pretty there's a few bugs lurking in there since it's VERY uncommon to
run into that sort of situation, but you are very welcomed to try to
root them out and submit the relevant jiras.
J-D
2011/3/18 Gaojinchao <ga...@huawei.com>:
> My cluster is 1'master and 2 region servers(RS1, RS2)
> In scenario as follow:
>
>
> 1、 start up the cluster and create table with some regions
>
> 2、 kill RS1 and RS2
>
> 3、 wait 30 minutes
>
> 4、 start up RS1
>
> 5、 wait about 3 hours
>
> 6、 start up RS2
>
> I find some regions can't be assigned
>
> The master print logs as：
>
> 2011-03-17 20:11:13,352 DEBUG org.apache.hadoop.hbase.master.CatalogJanitor: Scanned 1680 catalog row(s) and gc'd 0 unreferenced parent region(s)
> 2011-03-17 20:12:54,541 INFO org.apache.hadoop.hbase.master.LoadBalancer: Skipping load balancing. servers=2 regions=837 average=418.5 mostloaded=419 leastloaded=419
> 2011-03-17 20:13:51,380 DEBUG org.apache.hadoop.hbase.client.MetaScanner: Scanning .META. starting at row= for max=2147483647 rows
> 2011-03-17 20:13:51,380 DEBUG org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation: Cache hit for row <> in tableName .META.: location server t6.site:60020, location region name .META.,,1.1028785192
> 2011-03-17 20:16:13,339 DEBUG org.apache.hadoop.hbase.master.CatalogJanitor: Scanned 1680 catalog row(s) and gc'd 0 unreferenced parent region(s)
> 2011-03-17 20:16:48,745 DEBUG org.apache.hadoop.hbase.client.MetaScanner: Scanning .META. starting at row= for max=2147483647 rows
> 2011-03-17 20:16:48,745 DEBUG org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation: Cache hit for row <> in tableName .META.: location server t6.site:60020, location region name .META.,,1.1028785192
> 2011-03-17 20:17:54,541 INFO org.apache.hadoop.hbase.master.LoadBalancer: Skipping load balancing. servers=2 regions=837 average=418.5 mostloaded=419 leastloaded=419
>
Re: some regions can't be assigned
Posted by Gaojinchao <ga...@huawei.com>.
This is a feedback :
the hadoop without append causes led to a bad result. When Rs crashed, the server info in META is not updated.
in hbase version 0.20.6, it always check META state in Metascan thread.
But in 0.90.1 , It does not exist.
In other cluster with append patch is testing the scenario.
-----邮件原件-----
发件人: jdcryans@gmail.com [mailto:jdcryans@gmail.com] 代表 Jean-Daniel Cryans
发送时间: 2011年3月22日 4:50
收件人: user@hbase.apache.org
主题: Re: some regions can't be assigned
So you are testing a case where the master ends up being alone? I'm
pretty there's a few bugs lurking in there since it's VERY uncommon to
run into that sort of situation, but you are very welcomed to try to
root them out and submit the relevant jiras.
J-D
2011/3/18 Gaojinchao <ga...@huawei.com>:
> My cluster is 1'master and 2 region servers(RS1, RS2)
> In scenario as follow:
>
>
> 1、 start up the cluster and create table with some regions
>
> 2、 kill RS1 and RS2
>
> 3、 wait 30 minutes
>
> 4、 start up RS1
>
> 5、 wait about 3 hours
>
> 6、 start up RS2
>
> I find some regions can't be assigned
>
> The master print logs as：
>
> 2011-03-17 20:11:13,352 DEBUG org.apache.hadoop.hbase.master.CatalogJanitor: Scanned 1680 catalog row(s) and gc'd 0 unreferenced parent region(s)
> 2011-03-17 20:12:54,541 INFO org.apache.hadoop.hbase.master.LoadBalancer: Skipping load balancing. servers=2 regions=837 average=418.5 mostloaded=419 leastloaded=419
> 2011-03-17 20:13:51,380 DEBUG org.apache.hadoop.hbase.client.MetaScanner: Scanning .META. starting at row= for max=2147483647 rows
> 2011-03-17 20:13:51,380 DEBUG org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation: Cache hit for row <> in tableName .META.: location server t6.site:60020, location region name .META.,,1.1028785192
> 2011-03-17 20:16:13,339 DEBUG org.apache.hadoop.hbase.master.CatalogJanitor: Scanned 1680 catalog row(s) and gc'd 0 unreferenced parent region(s)
> 2011-03-17 20:16:48,745 DEBUG org.apache.hadoop.hbase.client.MetaScanner: Scanning .META. starting at row= for max=2147483647 rows
> 2011-03-17 20:16:48,745 DEBUG org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation: Cache hit for row <> in tableName .META.: location server t6.site:60020, location region name .META.,,1.1028785192
> 2011-03-17 20:17:54,541 INFO org.apache.hadoop.hbase.master.LoadBalancer: Skipping load balancing. servers=2 regions=837 average=418.5 mostloaded=419 leastloaded=419
>