[
https://issues.apache.org/jira/browse/HBASE-9076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David S. Wang updated HBASE-9076:
---------------------------------
Resolution: Duplicate
Status: Resolved (was: Patch Available)
> Throttle log messages for missing peer cluster
> ----------------------------------------------
>
> Key: HBASE-9076
> URL: https://issues.apache.org/jira/browse/HBASE-9076
> Project: HBase
> Issue Type: Improvement
> Components: Replication
> Affects Versions: 0.95.1, 0.94.10
> Reporter: David S. Wang
> Assignee: David S. Wang
> Priority: Trivial
> Attachments: HBASE-9076.patch
>
>
> If the replication peer is not available, then RS logs get flooded by
> messages similar to the following:
> 2013-07-19 11:55:27,964 INFO
> org.apache.hadoop.hbase.replication.regionserver.ReplicationSource: Getting 0
> rs from peer cluster # Indexer_hbaseIndexer
> 2013-07-19 11:55:28,670 INFO
> org.apache.hadoop.hbase.replication.regionserver.ReplicationSource: Getting 0
> rs from peer cluster # Indexer_hbaseIndexer
> 2013-07-19 11:55:28,966 INFO
> org.apache.hadoop.hbase.replication.regionserver.ReplicationSource: Getting 0
> rs from peer cluster # Indexer_hbaseIndexer
> 2013-07-19 11:55:29,672 INFO
> org.apache.hadoop.hbase.replication.regionserver.ReplicationSource: Getting 0
> rs from peer cluster # Indexer_hbaseIndexer
> 2013-07-19 11:55:29,969 INFO
> org.apache.hadoop.hbase.replication.regionserver.ReplicationSource: Getting 0
> rs from peer cluster # Indexer_hbaseIndexer
> It would be better to change the log level to DEBUG in order to avoid these
> messages showing up in the default case.
--
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
