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 Sat, 31 Oct 2015 20:53:27 GMT

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

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

bq. Replication should quit and give up when the destination or source are deleted

What do you mean by "quit"? Exit the tabletserver/master? Delete the records for the source+dest?

I think these are trickier than they appear at first glance.

Consider the case when a source table is deleted, what if there are pending files to be replicated
that a user did not realize. They thought the table was fully replicated elsewhere (where
the table is desired) and they are trying to clean up the table locally (where it is now unneeded).
We would want to make sure that we still replicate the data even if the source table no longer
exists. There may be some issues because the configuration required to replicate the table
is now missing. Perhaps this can be mitigated with better documentation/tools on when a table
is fully replicated.

If a destination doesn't exist, this could indicate misconfiguration. This may be transient
(especially in the case if the user tried to update the configuration in ZK but the master
didn't notice it when it tried to run replication). I think we would want to be careful in
how we fail in this case as it can be corrected by user configuration.

> 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
>             Fix For: 1.7.1, 1.8.0
>
>
> 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