You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Xu Cang (JIRA)" <ji...@apache.org> on 2019/07/17 01:31:00 UTC

[jira] [Comment Edited] (HBASE-22639) Unexpected split when a big table has only one region on a regionServer

    [ https://issues.apache.org/jira/browse/HBASE-22639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16886604#comment-16886604 ] 

Xu Cang edited comment on HBASE-22639 at 7/17/19 1:30 AM:
----------------------------------------------------------

I don't quite catch what you meant here "don't split the region when table is big enough even it is the only one on a node." Can you please elaborate why you think this is a bad thing?

Why is splitting  "a big enough' table a bad thing? 

 

Thanks! 


was (Author: xucang):
I don't quite catch what you meant here "don't split the region when table is big enough even it is the only one on a node." Can you please elaborate why you think this is a bad thing? Thanks! 

> 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)