[ https://issues.apache.org/jira/browse/HBASE-12091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16234744#comment-16234744 ]
Lars Hofhansl commented on HBASE-12091: --------------------------------------- This is turning into a whole nightmare now. There's no way that I can find to transmit unadulterated data from the sink the source (or server to any client). I changed the sink to just throw a TableNotFoundException, but IPCUtil.createRemoteException adds the trace to the message, so the client would have parse the text to get the table, which is fragile. > 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.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)