[
https://issues.apache.org/jira/browse/HBASE-12091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16234608#comment-16234608
]
Lars Hofhansl commented on HBASE-12091:
---------------------------------------
Found that the test is not right. In branch-1 the sink no longer throws a
TableNotFoundException, so none of the logic is actually triggered. Will have a
fix (for the test) soon.
"hbase.replication.drop.on.deleted.tables" is much better. Thanks!
> 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
> Assignee: Lars Hofhansl
> Priority: Major
> Fix For: 1.4.0
>
> Attachments: 12091-v2-branch-1.txt, 12091-v3-branch-1.txt,
> 12091-v4-branch-1.txt, 12091.txt
>
>
> 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.4.14#64029)
