[
https://issues.apache.org/jira/browse/HBASE-1621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13081149#comment-13081149
]
Andy Sautins commented on HBASE-1621:
-------------------------------------
Would it be possible for the implementation to not have to compact before and
after the merge is done? Looking at HRegion.merge it starts by compacting
stores on both regions and then at the end compacts the stores for the new
merged region before completing. Would it be possible to just merge all the
store files and let the next major compaction on the new region handle store
compaction? It would be nice to keep the amount of time the table needs to be
disabled to a minimum. If one or both of the regions being merged is large it
could take a meaningful amount of time to complete the merge.
> 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
