hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Wellington Chevreuil (Jira)" <j...@apache.org>
Subject [jira] [Resolved] (HBASE-24758) Avoid flooding replication source RSes logs when no sinks are available
Date Mon, 27 Jul 2020 12:26:00 GMT

     [ https://issues.apache.org/jira/browse/HBASE-24758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Wellington Chevreuil resolved HBASE-24758.
------------------------------------------
    Resolution: Fixed

Pushed to master, branch-2 and branch-2.3.

> 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)

Mime
View raw message