You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Appy (JIRA)" <ji...@apache.org> on 2018/02/21 23:16:00 UTC
[jira] [Updated] (HBASE-15740) Replication source.shippedKBs metric
is undercounting because it is in KB
[ https://issues.apache.org/jira/browse/HBASE-15740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Appy updated HBASE-15740:
-------------------------
Release Note: Removed Replication source.shippedKBs metric in favor of source.shippedBytes (was: Deprecated Replication source.shippedKBs metric in favor of source.shippedBytes)
> Replication source.shippedKBs metric is undercounting because it is in KB
> -------------------------------------------------------------------------
>
> Key: HBASE-15740
> URL: https://issues.apache.org/jira/browse/HBASE-15740
> Project: HBase
> Issue Type: Sub-task
> Reporter: Enis Soztutar
> Assignee: Enis Soztutar
> Priority: Major
> Fix For: 2.0.0, 1.3.0, 0.98.20
>
> Attachments: HBASE-15740-0.98.patch, hbase-15740_v1.patch, hbase-15740_v2.patch
>
>
> In a cluster where there is replication going on, I've noticed that this is always 0:
> {code}
> "source.shippedKBs" : 0,
> {code}
> Looking at the source reveals why:
> {code}
> metrics.shipBatch(currentNbOperations, currentSize / 1024, currentNbHFiles);
> {code}
> It is always undercounting because we discard remaining bytes after KB boundary. This is specially a problem when we are always shipping small batches <1KB.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)