I have a table in Hbase that sizes around 96Gb,
I generate 4 regions of 30Gb. Some time, table starts to split because the
max size for region is 1Gb (I just realize of that, I'm going to change it
or create more pre-splits.).
There're two things that I don't understand. how is it creating the
There're some new regions that they're just a some KBytes!. Why they are so
small?? When does HBase decide to split? because it started to split two
hours later to create the table.
When hbase does a split, it doesn't actually split at the disk/file level.
Its just a metadata operation which
The default split policy in hbase0.94.x is IncreaseToUpperBound rather than
ConstantSizeSplitPolicy which was the default in the older versions of
hbase.
Please refer to the link given below to understand how a
IncreaseToUpperBoundSplitPolicy works:
I read the article, that's why I typed the question, because I didn't
understand the result I got.
Oh, yes!!, that's true, so silly.
I think some of the files are pretty small because the table has two
families and one of them is much smaller than the another one. So, it has
been splitted many
