[
https://issues.apache.org/jira/browse/HBASE-19441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16406436#comment-16406436
]
Ted Yu commented on HBASE-19441:
--------------------------------
{code}
[ERROR] TestBackupManager.org.apache.hadoop.hbase.backup.TestBackupManager
The HBaseClassTestRule ClassRule in
org.apache.hadoop.hbase.backup.TestBackupManager is for
org.apache.hadoop.hbase.backup.TestBackupSystemTable expected:<class
org.apache.hadoop.hbase.backup.TestBackupManager> but was:<class
org.apache.hadoop.hbase.backup.TestBackupSystemTable>
{code}
Looks like copy-paste error.
Add license header to ExclusiveOperationException, please.
> 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
>
>
> {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)
