[ https://issues.apache.org/jira/browse/HBASE-24758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17171749#comment-17171749 ]
Sean Busbey commented on HBASE-24758: ------------------------------------- why didn't this go to branch-2.2? > Avoid flooding replication source RSes logs when no sinks are available > ------------------------------------------------------------------------ > > Key: HBASE-24758 > URL: https://issues.apache.org/jira/browse/HBASE-24758 > Project: HBase > Issue Type: Improvement > Components: Replication > Affects Versions: 3.0.0-alpha-1, 2.3.1, 2.4.0, 2.2.5 > Reporter: Wellington Chevreuil > Assignee: Wellington Chevreuil > Priority: Major > Fix For: 3.0.0-alpha-1, 2.3.1, 2.4.0 > > > On HBaseInterClusterReplicationEndpoint.replicate, if no sinks are returned > by ReplicationSinkManager, say remote peer is not available, we log message > below and return false to source shipper thread, which then keeps retrying, > flooding source RS log with the below messages: > {noformat} > WARN > org.apache.hadoop.hbase.replication.regionserver.HBaseInterClusterReplicationEndpoint: > No replication sinks found, returning without replicating. The source should > retry with the same set of edits. > {noformat} > This condition could also cause ReplicationSinkManager.chooseSinks to blow an > NPE. -- This message was sent by Atlassian Jira (v8.3.4#803005)