[ https://issues.apache.org/jira/browse/HBASE-12091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16246254#comment-16246254 ]
Andrew Purtell commented on HBASE-12091: ---------------------------------------- bq. Looks like it's going through Protobufs builtin ServiceException, which is thrown internally. Ok, that may narrow what we can pass to the standard exception message strings. We can look at this more in another issue. The v8 patch looks good. +1 from me Mostly looked at the new tests. As far as I can tell, they cover what we are after. Something which may reduce running time and decrease the likelihood of unstable results is replacing that hardcoded sleep with subsequent verification checks to Waiters that incorporate those verification checks as wait termination conditions. Not important, but for your consideration. > 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: 2.0.0, 3.0.0, 1.4.1, 1.5.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-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 (v6.4.14#64029)