Description
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.
Attachments
Attachments
Issue Links
- breaks
-
HBASE-19972 Should rethrow the RetriesExhaustedWithDetailsException when failed to apply the batch in ReplicationSink
- Closed
- relates to
-
HBASE-22630 Restore TestReplicationDroppedTables coverage to branch-1
- Resolved