[
https://issues.apache.org/jira/browse/HADOOP-2405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12556694#action_12556694
]
Bryan Duxbury commented on HADOOP-2405:
---------------------------------------
So, you envision the merge operation to not only require manual triggering but
to require manual targeting? Shouldn't the point of merging regions be to
maintain the equilibrium of size of regions? Under what circumstances will you
have to manually intervene to keep regions appropriately sized?
It seems like this should really only happen after a substantial number of
deletions has occurred, right? That would cause a compacted region to shrink
below a healthy size, and if it could be merged with a neighbor, it would be
nice. This logic should be built in and automatic, otherwise it would require
constant monitoring of region sizes by an administrator.
Other than this sort of automatic merging, when would you want to manually
merge two regions? Doesn't that expose a somewhat dangerous amount of
functionality to the end user?
> [hbase] Merge region tool exposed in shell and/or in UI
> -------------------------------------------------------
>
> Key: HADOOP-2405
> URL: https://issues.apache.org/jira/browse/HADOOP-2405
> Project: Hadoop
> Issue Type: New Feature
> Components: contrib/hbase
> Reporter: stack
> Priority: Minor
>
> hbase has support for merging regions. Expose a merge trigger in the shell
> or in the UI (Can only merge adjacent features so perhaps only makes sense in
> UI in the regionserver UI).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
