accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-3818) replication should quit if the destination table does not exist
Date Wed, 01 Jun 2016 19:15:59 GMT

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

Josh Elser commented on ACCUMULO-3818:
--------------------------------------

bq. Perhaps we could improve Random Walk tests to prevent these errors? A new, more narrowly
scoped ticket could address that.

+1

bq. It doesn't appear that there's a clear and appropriate solution for a production use case.

We might be able to do something to make this fail "better", but we'd have to apply a bit
of thought to actually understand the problems, what should be retried (to avoid data loss),
etc.

> replication should quit if the destination table does not exist
> ---------------------------------------------------------------
>
>                 Key: ACCUMULO-3818
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-3818
>             Project: Accumulo
>          Issue Type: Bug
>          Components: master, tserver
>    Affects Versions: 1.7.0
>            Reporter: Eric Newton
>              Labels: 1.7.0_QA
>
> Restarting a replication Random Walk test, I noticed huge numbers of ERRORS: 
> RemoteReplicationException(code:TABLE_DOES_NOT_EXIST, reason:Table with id 3 does not
exist).
> Replication should quit and give up when the destination or source are deleted.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message