[PHOENIX-2762] Phoenix creating global index tables with MAX_FILESIZE of 11994435 (11.99 MB) when creating index on one column in a wide table.

• Type: Bug
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: 4.4.0, 4.5.0, 4.6.0, 4.7.0
• Labels: index secondaryIndex
• Assignee: Unassigned
• Reporter: Anil Gupta
• Created: 12/Mar/16 21:32
• Updated: 31/Aug/16 07:15

Description

We have set default MAX_FILESIZE=8GB on our cluster.
Main table has around 1100 columns. I create an index on one column. Max_filesize in secondary index table is set to 11.99MB ( i.e. (1/1100)*8GB) approximately .
This leads to excessive splitting of regions and a lot of regions for secondary index table.
So, i think, we need to set a lower bound on region size of secondary index tables in Phoenix.

I propose to have a Phoenix property(phoenix.global.index.maxfilesize.min) to set lower bound of max_filesize of secondary index table.

Please refer to this http://search-hadoop.com/m/9UY0h2DNmug2BAMko for details.

Issue Links

• is related to: PHOENIX-3228 Index tables should not be configured with a custom/smaller MAX_FILESIZE