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 Thu, 25 Sep 2014 17:07:34 GMT

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

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

This might not actually be as simple as it sounds to do efficiently.
We could trivially check whether the table does not exist at the slave by just checking the
exception returned. But that's not what we want. We to check whether the table exists on the
source, and for each edit that's expensive (a META or ZK lookup), so I'd need to build in
some kind of caching.


> 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