[
https://issues.apache.org/jira/browse/HBASE-12091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16227711#comment-16227711
]
Lars Hofhansl commented on HBASE-12091:
---------------------------------------
The problem seems to be that ProtobufUtil.replicateWALEntry already unwraps any
remote exception... But in HBaseInterClusterReplicationEndpoint.replicate we
want to distinguish between remote and local exceptions.
So now we lost the ability to filter for specific remote exceptions. Different
jira perhaps.
For this one it's annoying that the sink does not even throw a
TableNotFoundException anymore. It seems the entire replication logic needs a
review in 1.4 (and probably before in 1.3 as well).
> 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
> Fix For: 1.4.0
>
> Attachments: 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)
