[
https://issues.apache.org/jira/browse/PHOENIX-6104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17255398#comment-17255398
]
Viraj Jasani commented on PHOENIX-6104:
---------------------------------------
{quote}We should also look into why MetadataSplitPolicy is extended from
ConstantSizeRegionSplitPolicy, as opposed to SteppingSplitPolicy, which is the
default for HBase 2.
{quote}
{code:java}
/**
* A split policy determines when a region should be split.
* @see IncreasingToUpperBoundRegionSplitPolicy Default split policy since
* 0.94.0
* @see ConstantSizeRegionSplitPolicy Default split policy before 0.94.0
*/
{code}
And branch-1 still has default split policy as
IncreasingToUpperBoundRegionSplitPolicy only.
{code:java}
private static final Class<? extends RegionSplitPolicy>
DEFAULT_SPLIT_POLICY_CLASS = IncreasingToUpperBoundRegionSplitPolicy.class;
{code}
I think ConstantSizeRegionSplitPolicy is kept before 0.94 HBase was supported
by Phoenix early versions.
{quote}most folks in EU and Amer timezones are probably on PTO until then.
{quote}
Definitely. So far, I was going through HBASE-18229 to see why bestSplitPoint
was added while ignoring splitPoint provided in request.
> SplitSystemCatalogIT tests very unstable with Hbase 2.3
> -------------------------------------------------------
>
> Key: PHOENIX-6104
> URL: https://issues.apache.org/jira/browse/PHOENIX-6104
> Project: Phoenix
> Issue Type: Bug
> Components: core
> Affects Versions: 5.1.0
> Reporter: Istvan Toth
> Assignee: Istvan Toth
> Priority: Major
> Attachments: 6104-testouput.log
>
>
> The failure is in the test preparation code, where we split the system
> catalog table, and it seems to be a HBase issue, rather than a Phoenix one,
> but we need to track the issue.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
