[
https://issues.apache.org/jira/browse/HBASE-7183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13510116#comment-13510116
]
Sho Shimauchi commented on HBASE-7183:
--------------------------------------
Hi JD,
2 is fine as default but it should also be configurable, because the best
parameter depends on the size of a cluster.
Alerting when the log is rolled is good. I think the worst case scenario is
acceptable because network partition itself is really bad and user have to fix
the situation asap.
> print WARN message if hbase.replication.sizeOfLogQueue is too big
> -----------------------------------------------------------------
>
> Key: HBASE-7183
> URL: https://issues.apache.org/jira/browse/HBASE-7183
> Project: HBase
> Issue Type: Improvement
> Components: Replication
> Reporter: Sho Shimauchi
>
> A metric hbase.replication.sizeOfLogQueue may become big when replication is
> delaying.
> It would be useful if HBase prints WARN log which tells
> hbase.replication.sizeOfLogQueue is too big.
--
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
