[
https://issues.apache.org/jira/browse/HBASE-1621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13081151#comment-13081151
]
stack commented on HBASE-1621:
------------------------------
I was thinking of an implementation that just ensured that the regions to merge
were first all closed out on the cluster and then it'd create the new merge
region and just move the storefiles from the old regions into place under the
new merge region -- then deploy. No writing of new store files. Let any
compactions, etc., happen post assign.
> merge tool should work on online cluster, but disabled table
> ------------------------------------------------------------
>
> Key: HBASE-1621
> URL: https://issues.apache.org/jira/browse/HBASE-1621
> Project: HBase
> Issue Type: Bug
> Reporter: ryan rawson
> Assignee: stack
> Priority: Blocker
> Fix For: 0.92.0
>
> Attachments: 1621-trunk.txt, HBASE-1621-v2.patch, HBASE-1621.patch,
> hbase-onlinemerge.patch
>
>
> taking down the entire cluster to merge 2 regions is a pain, i dont see why
> the table or regions specifically couldnt be taken offline, then merged then
> brought back up.
> this might need a new API to the regionservers so they can take direction
> from not just the master.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
