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

Wellington Chevreuil commented on HBASE-23562:
----------------------------------------------

{quote}I'd like to see some differentiation to prevent this feature and the 
Region Normalizer from overlapping and causing confusion in "how do I reduce 
the regions in my cluster"?
{quote}
This tool provides a more interactive experience for operators. Also, region 
normalizer implementation logic merges regions based on an overall regions size 
average and an specific threshold, which just doesn't help majority of the 
cases where too many small regions exist due to a poor pre-split strategy or 
worse, when table is left with many overlapping regions.
{quote}Thinking about it quickly, I think if we focus the Normalizer on "slow, 
always-on, always correcting, low-user impact" and this tool on "Proactively 
merging many regions together, high-user impact, 'fast'", that's a decent 
distinction.
{quote}
Agreed. I would label Normalizer as a built-in, house keeping internal hbase 
process, while this one is a manual fix tool for operators (hence, that's why 
it's placed under operator tools project).

 

Any further ideas/suggestions in relation to the current PR?

> [operator tools] Add a RegionsMerge tool that allows for merging multiple 
> adjacent regions until a desired number of regions is reached.
> ----------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-23562
>                 URL: https://issues.apache.org/jira/browse/HBASE-23562
>             Project: HBase
>          Issue Type: New Feature
>          Components: hbase-operator-tools
>            Reporter: Wellington Chevreuil
>            Assignee: Wellington Chevreuil
>            Priority: Minor
>
> There's been a few occasions where different customers had faced the need to 
> reduce the number of regions for specific tables, either due to mistakenly 
> pre-split or after a purge in table data. This jira is for adding a simple 
> merge tool that takes the table name and the desired number of regions, then 
> perform region merges until the total number of regions for the given table 
> reached the passed valued. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to