[
https://issues.apache.org/jira/browse/HBASE-7183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13727521#comment-13727521
]
Hadoop QA commented on HBASE-7183:
----------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12595551/HBASE_7183.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/6571//console
This message is automatically generated.
> 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
> Labels: noob
> Attachments: HBASE_7183.patch
>
>
> 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
