Re: Can region be merged with others automatically when all data in the region has expired and removed ?

I'm curious, if you are expiring a lot of data, does your table grow? If not, could you fit it in to a mysql instance instead? As for pre-splitting tables, if you have a really large data set, how would you manage this? One of our tables has 700 regions, and we didnt pre-split. I didnt really know

Re: Can region be merged with others automatically when all data in the region has expired and removed ?

Online merge is a bit dangerous. Lots of applications require that the table be set up pre-split. This is probably more common than the need for merging. Having such a pre-split table collapse before it is full would be a disaster. It should be pretty easy to script taking a few regions off-lin

Hudson build is back to normal : HBase-TRUNK #1739

See

Build failed in Hudson: hbase-0.90 #81

See Changes: [todd] Revert HBASE-3470 since it breaks job submission (HBASE-3517) -- [...truncated 2684 lines...] Running org.apache.hadoop.hbase.master.TestHMasterRPCException Tests run: 1, Fail

Re: Can region be merged with others automatically when all data in the region has expired and removed ?

Definitely, but it's not a critical issue yet since most of the major users don't use TTL as far as I know. I would recommend setting your region bigger than the default if meta size is becoming an issue. An automatic online merge feature would be a nice contribution too. J-D On Feb 8, 2011 6:27

Re: Can region be merged with others automatically when all data in the region has expired and removed ?

I think this function may should be part of hbase in the future version. Or hbase may got problem when running long time. Too many regions will cause meta data too large and occupy too much memory. Zhou Shuaifeng(Frank) HUAWEI TECHNOLOGIES CO.,LTD. ---

Re: Can region be merged with others automatically when all data in the region has expired and removed ?

There's an offline tool called Merge that you can use at your own risk, but nothing currently will do it automagically. J-D On Tue, Feb 8, 2011 at 6:14 PM, Zhou Shuaifeng wrote: > If not, there may be many empty or very small regions, and it will cause > meta data too large. > > > > Zhou Shuaife

Can region be merged with others automatically when all data in the region has expired and removed ?

If not, there may be many empty or very small regions, and it will cause meta data too large. Zhou Shuaifeng(Frank) - This e-mail and its attachments contai

Re: Loaded Coprocessor

Hi JS. Here are some hints to help you debug: - make sure you have the jar copied to all the region servers if you want it to sit on local fs, or you can put it to hdfs so all RS can access it without copying arount. - remember to disable, and enable the table to make sure the attribute be lo

Re: Loaded Coprocessor

Hi, thanks for your feedback! Just a follow up question; According to the TableDescriptor {NAME => 'test3', Coprocessor$2 => '/Users/hbase/CP.jar:Coprocessor.PreGet:12', Coprocessor$1 => '/Users/hbase/CP.jar:Coprocessor.PrePut:10', FAMILIES => [{NAME => 'cf', BLOOMFILTER => 'NONE', REPLICATION_

Build failed in Hudson: HBase-TRUNK #1738

See Changes: [stack] Minor fixup on timeseries section [stack] HBASE-3499 Users upgrading to 0.90.0 need to have their .META. table updated with the right MEMSTORE_SIZE -- [...truncated 2934