[
https://issues.apache.org/jira/browse/HBASE-12091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16236317#comment-16236317
]
Andrew Purtell commented on HBASE-12091:
----------------------------------------
I'm going to need a patch for master / branch-2. I did a naive forward port and
the new test fails. Looks like this is where you can start
2017-11-02 18:17:29,857 WARN
[RS:0;ip-172-31-47-35:40602.replicationSource.ip-172-31-47-35.us-west-2.compute.internal%2C40602%2C1509646634367,2]
regionserver.HBaseInterClusterReplicationEndpoint(363): Can't replicate
because of an error on the remote cluster:
org.apache.hadoop.hbase.client.RetriesExhaustedWithDetailsException:
org.apache.hadoop.hbase.client.RetriesExhaustedWithDetailsException: Failed
1000 actions: Region of
'test,zzz,1509646631231.30b4d78ffe0dd1640ea4ac555f8b8583.' is expected in the
table of 'test_dropped', but hbase:meta says it is in the table of 'test'.
hbase:meta might be damaged.: 1000 times, servers with issues: null
> 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)
