[
https://issues.apache.org/jira/browse/HBASE-7735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13610997#comment-13610997
]
Enis Soztutar commented on HBASE-7735:
--------------------------------------
bq. terry zhang, there definitely is a comment in the code about coordinating
using the region name list as opposed to the region server list (legacy of the
initial implementation) and is similar to what you are suggesting. Doing that
could make snapshots robust in the face of region moves – a region moves but it
is till the same region. I think with the approach you suggest splits will
cause failure still.
If we get HBASE-7848 in, then during the snapshot it would mean that the list
of regions can't change (due to splits, and merges (HBASE-7977)). Then by
changing the spapshot to be based on list of regions should suffice, no?
> Prevent regions from moving during online snapshot.
> ---------------------------------------------------
>
> Key: HBASE-7735
> URL: https://issues.apache.org/jira/browse/HBASE-7735
> Project: HBase
> Issue Type: Sub-task
> Reporter: Jonathan Hsieh
>
> To increase the probability of snapshots succeeding, we should attempt to
> prevent splits and region moves from happening. Currently we take region
> locks but this could be "too late" and results in an aborted snapshot.
> We should probably take the table lock (0.96) when starting a snapshot and
> for a 0.94 backport we should probably disable the balancer.
> This will probably not be tackled until after trunk merge.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
