[
https://issues.apache.org/jira/browse/HBASE-10213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13853941#comment-13853941
]
Hadoop QA commented on HBASE-10213:
-----------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12619783/HBASE-10213-0.94-v1.patch
against trunk revision .
ATTACHMENT ID: 12619783
{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/8242//console
This message is automatically generated.
> Add read log size per second metrics for replication source
> -----------------------------------------------------------
>
> Key: HBASE-10213
> URL: https://issues.apache.org/jira/browse/HBASE-10213
> Project: HBase
> Issue Type: Improvement
> Components: metrics, Replication
> Affects Versions: 0.94.14
> Reporter: cuijianwei
> Assignee: cuijianwei
> Priority: Minor
> Attachments: HBASE-10213-0.94-v1.patch
>
>
> The current metrics of replication source contain logEditsReadRate,
> shippedBatchesRate, etc, which could indicate how fast the data replicated to
> peer cluster to some extent. However, it is not clear enough to know how many
> bytes replicating to peer cluster from these metrics. In production
> environment, it may be important to know the size of replicating data per
> second because the services may be affected if the network become busy.
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
