Re: Excessive region splitting of Global Index table(8 Megabyte regions)

Yes, good idea. Please file a JIRA. On Sat, Mar 12, 2016 at 1:07 PM, anil gupta wrote: > To provide more insight, This table has around 1100 columns. I create this > index on one column. (1/1100) * 8GB comes around 8MB. So, i think, we need > to set a lower bound on

Re: Excessive region splitting of Global Index table(8 Megabyte regions)

Thanks for the reply, James. We have 2 global secondary index in this table and both of them exhibit same behavior. Going to give your suggestion a try. I also think that regionsize for secondary index should not be 8GB. Will try to set the regionsize=1GB for secondary index and see how it goes.

Re: Excessive region splitting of Global Index table(8 Megabyte regions)

Hi Anil, Phoenix estimates the ratio between the data table and index table as shown below to attempt to get the same number of splits in your index table as your data table. /* * Approximate ratio between index table size and data table size: * More or less equal to the ratio between the

Excessive region splitting of Global Index table(8 Megabyte regions)

Hi, We are using HDP2.3.4 and Phoenix4.4. Our global index table is doing excessive splitting. Our cluster region size setting is 8 Gigabytes but global index table has 18 regions and max size of region is 10.9 MB. This is definitely not a good behavior. I looked into tuning (