[
https://issues.apache.org/jira/browse/HBASE-19441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16408172#comment-16408172
]
Josh Elser commented on HBASE-19441:
------------------------------------
{quote}
bq. Why is this illegal import, Ted Yu?
I think the package from com.google.common.util is not shaded :
{quote}
Right. The full answer is that we've moved dependencies which tend to have
compatibility issues into the hbase-thirdparty project. In this project, we
shade these dependencies to help insulate us from other JARs that happen to
make it onto the runtime classpath. Thus, we want to make sure that we're using
these shaded variants -- that's what this checkstyle rule is telling us: we're
using the non-shaded path to these classes instead of the shaded path we want.
> 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: 19441-v5.patch, 19441-v6.patch, 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)
