[
https://issues.apache.org/jira/browse/HBASE-12091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16236217#comment-16236217
]
Andrew Purtell commented on HBASE-12091:
----------------------------------------
bq. It's ugly, though. The code needs to parse out the table name from the
exception, it double checks that it got a valid table-name, and check back for
a local table...
Yeah, that's how it works - for now. File an improvement issue for that?
As for this issue, let me try committing it back to branch-1.4. I'll come back
here if there is a problem, otherwise will commit today.
> 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-v5-branch-1.txt, 12091-v6-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)
