[ https://issues.apache.org/jira/browse/HBASE-7280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13685495#comment-13685495 ]
Feng Honghua commented on HBASE-7280: ------------------------------------- [~jeason] You can refer to HBASE-8751 for per-peer cf/table granularity replication > TableNotFoundException thrown in peer cluster will incur endless retry for > shipEdits, which in turn block following normal replication > -------------------------------------------------------------------------------------------------------------------------------------- > > Key: HBASE-7280 > URL: https://issues.apache.org/jira/browse/HBASE-7280 > Project: HBase > Issue Type: Bug > Components: Replication > Affects Versions: 0.94.2 > Reporter: Feng Honghua > Original Estimate: 0.5h > Remaining Estimate: 0.5h > > in cluster replication, if the master cluster have 2 tables which have > column-family declared with replication scope = 1, and add a peer cluster > which has only 1 table with the same name as the master cluster, in the > ReplicationSource (thread in master cluster) for this peer, edits (logs) for > both tables will be shipped to the peer, the peer will fail applying the > edits due to TableNotFoundException, and this exception will also be > responsed to the original shipper (ReplicationSource in master cluster), and > the shipper will fall into an endless retry for shipping the failed edits > without proceeding to read the remained(newer) log files and to ship > following edits(maybe the normal, expected edit for the registered table). > the symptom looks like the TableNotFoundException incurs endless retry and > blocking normal table replication -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira