hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Purtell (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-10213) Add read log size per second metrics for replication source
Date Tue, 31 Dec 2013 02:59:50 GMT

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

Andrew Purtell updated HBASE-10213:
-----------------------------------

    Fix Version/s: 0.98.0

Committed to 0.98. Thanks Ted.

I fixed a spelling error on commit. Attached is an addendum for trunk to match what went into
0.98. I committed this trivial change to trunk using CTR as r1554361.

[~stack] and [~lhofhansl]: We can close this after a decision on 0.96 and 0.94. Almost feel
bad pinging you, should be no big deal.

> 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
>             Fix For: 0.98.0, 0.99.0
>
>         Attachments: 10213-trunk-addendum-1.patch, HBASE-10213-0.94-v1.patch, HBASE-10213-0.94-v2.patch,
HBASE-10213-trunk-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.5#6160)

Mime
View raw message