[ https://issues.apache.org/jira/browse/HBASE-12091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16227684#comment-16227684 ]
Lars Hofhansl commented on HBASE-12091: --------------------------------------- [~apurtell], FYI. Might be something to check to 1.4. Specifically it seems I cannot produce a test that shows that edits are ordered correctly in the face of dropped tables. > 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 > 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)