[
https://issues.apache.org/jira/browse/PHOENIX-1402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14196375#comment-14196375
]
James Taylor commented on PHOENIX-1402:
---------------------------------------
It's possible, but I'm not sure how it would manifest itself. At write time is
when you'd see lots of splits. By recalculating stats during splits, we're
delaying finishing a split which might in turn cause these errors. Or,
alternatively, perhaps it's just doing a lot of splits initially and having a
hard time keeping up. Do you have the logs for this, as we could look for
evidence of this there. Any thoughts, [~lhofhansl]?
> Don't recalculate stats on split
> --------------------------------
>
> Key: PHOENIX-1402
> URL: https://issues.apache.org/jira/browse/PHOENIX-1402
> Project: Phoenix
> Issue Type: Bug
> Reporter: James Taylor
>
> Rather than scan the new regions on a split (which is potentially expensive,
> and might be causing the timeouts you're seeing [~jfernando_sfdc]), we should
> instead just split up the existing guideposts between new two new regions
> based on the split point.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
