+1 with what Heng said. I think we should just deprecate the ability to not pre-split a table ;) It's always good to pre-split it based on your key design...
2016-03-16 0:17 GMT-04:00 Heng Chen <[email protected]>: > bq. the table I created by default having only one region > > Why not pre-split table into more regions when create it? > > 2016-03-16 11:38 GMT+08:00 Ted Yu <[email protected]>: > > > When one region is split into two, both daughter regions are opened on > the > > same server where parent region was opened. > > > > Can you provide a bit more information: > > > > release of hbase > > whether balancer was turned on - you can inspect master log to see if > > balancer was on > > > > Consider pastebinning portion of master log. > > > > Thanks > > > > On Tue, Mar 15, 2016 at 4:43 PM, jackwang <[email protected]> > wrote: > > > > > I was writing 300GiB data to my Hbase table user_info, the table I > > created > > > by > > > default having only one region. When the writing was going I saw one > > region > > > became two regions and more late on it became 8 regions. But my > confusion > > > is > > > that the 8 regions were kept in the same RegionServer. > > > > > > Why Hbase didn't split the regions to different RegionServer. btw, I > had > > 10 > > > physical RegionsServers in my Hbase cluster, and the region size I set > is > > > 20GiB, Thanks! > > > > > > > > > > > > -- > > > View this message in context: > > > > > > http://apache-hbase.679495.n3.nabble.com/why-Hbase-only-split-regions-in-one-RegionServer-tp4078497.html > > > Sent from the HBase User mailing list archive at Nabble.com. > > > > > >
