You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@hbase.apache.org by "Ted Yu (JIRA)" <ji...@apache.org> on 2016/12/14 18:37:58 UTC

[jira] [Resolved] (HBASE-16579) Concurrent backup / restore support

     [ https://issues.apache.org/jira/browse/HBASE-16579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ted Yu resolved HBASE-16579.
----------------------------
    Resolution: Later

With dramatic refactoring, this may require significant amount of work.

> Concurrent backup / restore support
> -----------------------------------
>
>                 Key: HBASE-16579
>                 URL: https://issues.apache.org/jira/browse/HBASE-16579
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Ted Yu
>              Labels: backup
>
> Currently we take exclusive lock on hbase:backup table in backup / restore procedures.
> There is only one backup or restore operation which can run at given time.
> We should consider using shared lock on hbase:backup table in the procedures so that concurrent backup / restore operations can proceed.
> The concurrency is useful when table sets don't overlap.
> We may devise other mechanism(s) when there is overlap among the table sets.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)