create simple m/r job to migrate data to new tables and drop the old ones。
Could you put your code paste to here? On Wed, Jul 13, 2011 at 7:43 AM, Ravi Veeramachaneni < ravi.veeramachan...@gmail.com> wrote: > Albert, > > You doing partially right. The change will take into effect only to new > tables created going forward. There are two options I'm aware of, 1. Use > alter command on HBase shell to specify new region size. 2. Create new set > of tables and create simple m/r job to migrate data to new tables and drop > the old ones. > > We followed the second approach when we bump the region size. The first > approach leaves the current region count But fills up until region gets to > 1GB. Our goal was to reduce number of regions to minimum, second approach > worked well for us. > > Thanks, > Ravi > > Sent from my mobile phone. > > On Jul 11, 2011, at 8:56 PM, Albert Shau <as...@yahoo-inc.com> wrote: > > > Hi everyone, > > > > I'm using 0.90.3 and have the region max filesize set to 1gb in my > hbase-site.xml like so: > > > > <property> > > <name>hbase.hregion.max.filesize</name> > > <value>1073741824</value> > > </property> > > > > But when I look at the storefileSizeMB values listed on the regionserver > UI, they're all around 256mb, which makes me think the default value is > still being used for whatever reason. I'm also setting other properties > like the handler count which are getting used so I'm pretty sure I have the > conf in the right place and it's getting read. I've also tried restarting > hbase and doing a major compact on the table but the region sizes stay the > same. Any ideas on what might be wrong? Is there some way to verify the > max filesize is getting set correctly? > > > > Thanks, > > Albert > > > -- Thanks & Best regards jiajun
