hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lars Hofhansl (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-12091) Optionally ignore edits for dropped tables for replication.
Date Sat, 04 Jul 2015 00:14:04 GMT

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

Lars Hofhansl commented on HBASE-12091:
---------------------------------------

Another option to do this: Wait until we actually get a TableNotFound exception from the sink.
When that happens check whether this one table exists on the source and ignore all edit for
this table for the retry. The disadvantage is that we're trying at least twice in this case
(but the case is rare).

> Optionally ignore edits for dropped tables for replication.
> -----------------------------------------------------------
>
>                 Key: HBASE-12091
>                 URL: https://issues.apache.org/jira/browse/HBASE-12091
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Lars Hofhansl
>
> We just ran into a scenario where we dropped a table from both the source and the sink,
but the source still has outstanding edits that now it could not get rid of. Now all replication
is backed up behind these unreplicatable edits.
> We should have an option to ignore edits for tables dropped at the source.



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

Mime
View raw message