[
https://issues.apache.org/jira/browse/HBASE-5292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-5292:
-------------------------
Fix Version/s: (was: 0.95.0)
0.94.2
Fix up after bulk move overwrote some 0.94.2 fix versions w/ 0.95.0 (Noticed by
Lars Hofhansl)
> getsize per-CF metric incorrectly counts compaction related reads as well
> --------------------------------------------------------------------------
>
> Key: HBASE-5292
> URL: https://issues.apache.org/jira/browse/HBASE-5292
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.89.20100924
> Reporter: Kannan Muthukkaruppan
> Fix For: 0.94.2
>
> Attachments:
> 0001-jira-HBASE-5292-Prevent-counting-getSize-on-compacti.patch,
> 5292-0.94.txt, ASF.LICENSE.NOT.GRANTED--D1527.1.patch,
> ASF.LICENSE.NOT.GRANTED--D1527.2.patch,
> ASF.LICENSE.NOT.GRANTED--D1527.3.patch,
> ASF.LICENSE.NOT.GRANTED--D1527.4.patch,
> ASF.LICENSE.NOT.GRANTED--D1617.1.patch,
> jira-HBASE-5292-Prevent-counting-getSize-on-compacti-2012-03-09_13_26_52.patch
>
>
> The per-CF "getsize" metric's intent was to track bytes returned (to HBase
> clients) per-CF. [Note: We already have metrics to track # of HFileBlock's
> read for compaction vs. non-compaction cases -- e.g., compactionblockreadcnt
> vs. fsblockreadcnt.]
> Currently, the "getsize" metric gets updated for both client initiated
> Get/Scan operations as well for compaction related reads. The metric is
> updated in StoreScanner.java:next() when the Scan query matcher returns an
> INCLUDE* code via a:
> HRegion.incrNumericMetric(this.metricNameGetsize, copyKv.getLength());
> We should not do the above in case of compactions.
--
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
