[
https://issues.apache.org/jira/browse/PHOENIX-3228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15451412#comment-15451412
]
Ankit Singhal commented on PHOENIX-3228:
----------------------------------------
IMO, I also think that we should remove this . As it can lead to excessive
splitting if not estimated well(relates to PHOENIX-2762).
And ,also it seems default policy "IncreasingToUpperBoundRegionSplitPolicy"
should be good enough to decide splitting of regions based on number of regions
per regionserver and flush size.(we will have some regions ranging from flush
size to MAX_FILESIZE).
if required , I think we should test again as with guideposts and considering
the fact that full table scan is not generally happen in case of Index.
> Index table are configured with a custom/smaller MAX_FILESIZE
> -------------------------------------------------------------
>
> Key: PHOENIX-3228
> URL: https://issues.apache.org/jira/browse/PHOENIX-3228
> Project: Phoenix
> Issue Type: Sub-task
> Reporter: Lars Hofhansl
> Assignee: Lars Hofhansl
> Fix For: 4.9.0, 4.8.1
>
> Attachments: 3228-remove.txt, 3228.txt
>
>
> I do not think we should do this. The default of 10G is chosen to keep HBase
> happy. For smaller tables or initially until the index gets large it might
> lead to more index regions and hence be able to utilize more region server,
> but generally, this is not the right thing to do.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
