[
https://issues.apache.org/jira/browse/HBASE-22639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16884276#comment-16884276
]
Zheng Wang commented on HBASE-22639:
------------------------------------
I did some test for it .
My test env has 5 nodes,and my test table has 15 regions,each node has 3
regions.
I moved 2 regions from node1 to node2,and then execute major_compact the last
region on node1, it splited to 2 region.
I couldn't reproduce it by restart node,but it may happen theoretically,and
happened in my live env in fact.
My advice is make an improvement of SteppingSplitPolicy , don't split the
region when table is big enough even it is the only one on a node.
> Unexpected split when a big table has only one region on a regionServer
> ------------------------------------------------------------------------
>
> Key: HBASE-22639
> URL: https://issues.apache.org/jira/browse/HBASE-22639
> Project: HBase
> Issue Type: Improvement
> Components: regionserver
> Affects Versions: 2.0.0
> Reporter: Zheng Wang
> Priority: Minor
>
> I am using the default policy named SteppingSplitPolicy.
> If restart some nodes,it may occur,because this policy didnot judge if the
> table is big enough actually.
> It brings some unexpected small regions.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
