Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hbase.apache.org
Date: Wed, 14 Dec 2016 18:37:58 +0000 (UTC)
From: "Ted Yu (JIRA)" <jira@apache.org>
To: dev@hbase.apache.org
Message-ID: <JIRA.13003394.1473287780000.521812.1481740678503@Atlassian.JIRA>
In-Reply-To: <JIRA.13003394.1473287780000@Atlassian.JIRA>
References: <JIRA.13003394.1473287780000@Atlassian.JIRA> <JIRA.13003394.1473287780502@arcas>
Subject: [jira] [Resolved] (HBASE-16579) Concurrent backup / restore support
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 14 Dec 2016 18:38:00 -0000


     [ 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)