[HBASE-19441] Implement retry logic around starting exclusive backup operation

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 3.0.0-alpha-1
• Component/s: backup&restore
• Hadoop Flags: Reviewed
• Assignee: Vladimir Rodionov
• Reporter: Josh Elser
• Created: 06/Dec/17 17:07
• Updated: 28/Mar/18 02:51
• Resolved: 21/Mar/18 16:35

Description

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().

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.

Issue Links

• is part of: HBASE-17362 HBase Backup/Restore Phase 4