[ 
https://issues.apache.org/jira/browse/HBASE-19441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16400736#comment-16400736
 ] 

Ted Yu commented on HBASE-19441:
--------------------------------

Comparing the text of exception is vulnerable to future change w.r.t. the 
message.

You can create a new exception class and check against the (new) class.

> 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
>            Priority: Major
>             Fix For: 3.0.0
>
>         Attachments: HBASE-19441-v1.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)

Reply via email to