It doesn't work!
I would like META table can split by table name.
If I have 10 tables, there are 10 regions in META that can be dispatched
to different region server, so I can start many
clients concurrently read different tables' data without META's bottleneck.
I had started 2000 concurrent hbase java cleints to get only one
table's(187 regions ) META,
which took 302 sec.
What I want to do is to improve the META performance by splitting the META.
Fleming Chiu(邱宏明)
707-6128
y_823...@tsmc.com
週一無肉日吃素救地球(Meat Free Monday Taiwan)
saint....@gmail.c
om To:
hbase-user@hadoop.apache.org
Sent by: cc: (bcc: Y_823910/TSMC)
saint....@gmail.c Subject: Re: Split META manually
om
2010/03/12 02:01
PM
Please respond to
hbase-user
Why split .META.? I'm not sure it works properly so would advise
against it (We don't have tests in place for that... we've not been
too concerned about it up to this since your install would have to be
massive for .META. to split).
St.Ack
2010/3/11 <y_823...@tsmc.com>:
> Hi there,
>
> I want to split META table manually but I wonder how to set the optional
> Region Key in the webpage.
> (using the value like BIG_TABLE,FRPFXRD_NF61904-0
> 1.001.Main.0,1268309701214)
>
> BIG_TABLE,FRPFXRD_NF61904-0 column=info:regioninfo,
> timestamp=1268309711446, value=REGION => {NAME => 'BIG_TA
> 1.001.Main.0,1268309701214
> BLE,FRPFXRD_NF61904-01.001.Main.0,1268309701214', STARTKEY =>
> 'FRPFXRD_NF61904-01
> .001.Main.0', ENDKEY =>
> 'FRPFXRD_NG50972-01.001.Main.1', ENCODED => 1864321617, T
>
> There is only one region in our META table now , if I want to split it by
> each table start key,
> is that possible? Thus it can release the META's bottleneck while
multiple
> clients reading request.
> Any ideas?
>
>
>
>
>
>
>
>
> Fleming Chiu(邱宏明)
> 707-6128
> y_823...@tsmc.com
> 週一無肉日吃素救地球(Meat Free Monday Taiwan)
>
>
>
---------------------------------------------------------------------------
> TSMC PROPERTY
> This email communication (and any attachments) is proprietary
information
> for the sole use of its
> intended recipient. Any unauthorized review, use or distribution by
anyone
> other than the intended
> recipient is strictly prohibited. If you are not the intended
recipient,
> please notify the sender by
> replying to this email, and then delete this email and any copies of it
> immediately. Thank you.
>
---------------------------------------------------------------------------
>
>
>
>
---------------------------------------------------------------------------
TSMC PROPERTY
This email communication (and any attachments) is proprietary information
for the sole use of its
intended recipient. Any unauthorized review, use or distribution by anyone
other than the intended
recipient is strictly prohibited. If you are not the intended recipient,
please notify the sender by
replying to this email, and then delete this email and any copies of it
immediately. Thank you.
---------------------------------------------------------------------------
