[
https://issues.apache.org/jira/browse/HBASE-19441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16407306#comment-16407306
]
Ted Yu commented on HBASE-19441:
--------------------------------
Among the checkstyle warnings, this must be addressed:
{code}
./hbase-backup/src/test/java/org/apache/hadoop/hbase/backup/TestBackupManager.java:44:import
com.google.common.util.concurrent.Uninterruptibles;:1: Import from illegal
package - com.google.common.util.concurrent.Uninterruptibles. [IllegalImport]
{code}
> Implement retry logic around starting exclusive backup operation
> ----------------------------------------------------------------
>
> Key: HBASE-19441
> URL: https://issues.apache.org/jira/browse/HBASE-19441
> Project: HBase
> Issue Type: Improvement
> Components: backup&restore
> Reporter: Josh Elser
> Assignee: Vladimir Rodionov
> Priority: Major
> Fix For: 3.0.0
>
> Attachments: HBASE-19441-v1.patch, HBASE-19441-v2.patch,
> HBASE-19441-v3.patch, HBASE-19441-v4.patch, HBASE-19441-v5.patch
>
>
> {quote}
> Specifically, the client does a checkAndPut to specifics coordinates in the
> backup table and throws an exception when that fails. Remember that backups
> are client driven (per some design review from a long time ago), so queuing
> is tough to reason about (we have no "centralized" execution system to use).
> At a glance, it seems pretty straightforward to add some retry/backoff
> semantics to BackupSystemTable#startBackupExclusiveOperation().
> {quote}
> While we are in a state in which backup operations cannot be executed in
> parallel, it would be nice to provide some retry logic + configuration. This
> would alleviate users from having to build this themselves.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
