[
https://issues.apache.org/jira/browse/HBASE-12091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16359428#comment-16359428
]
Duo Zhang commented on HBASE-12091:
-----------------------------------
{code}
catch (RetriesExhaustedWithDetailsException rewde) {
for (Throwable ex : rewde.getCauses()) {
if (ex instanceof TableNotFoundException) {
throw new TableNotFoundException("'" + tableName + "'");
}
}
}
{code}
This is new piece of code added to ReplicationSink.batch. So we will only
rethrow the exception if it is a TableNotFound? And for other exceptions we
will just ignore? Is this intentional or just a typo?
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: 2.0.0, 3.0.0, 1.4.0
>
> Attachments: 12091-branch-2.patch, 12091-v2-branch-1.txt,
> 12091-v3-branch-1.txt, 12091-v4-branch-1.txt, 12091-v5-branch-1.txt,
> 12091-v6-branch-1.txt, 12091-v7-branch-1.txt, 12091-v7-master.txt,
> 12091-v8-branch-1.txt, 12091-v8-master.txt, 12091-v9-branch-1.txt,
> 12091-v9-master.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
(v7.6.3#76005)
