[HBASE-6377] HBASE-5533 metrics miss all operations submitted via MultiAction

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.94.1, 0.95.2
• Fix Version/s: 0.94.1, 0.95.0
• Component/s: metrics, regionserver
• Hadoop Flags: Reviewed
• Release Note: The misleading "getRequestLatency", "deleteRequestLatency", and "putRequestLatency" histograms were removed from metrics because such requests often were not actually measured.
• Assignee: Andrew Kyle Purtell
• Reporter: Andrew Kyle Purtell
• Created: 12/Jul/12 02:19
• Updated: 29/Jul/14 03:07
• Resolved: 13/Jul/12 01:05

Description

A client application (LoadTestTool) calls put() on HTables. Internally to the HBase client those puts are batched into MultiActions. The total number of put operations shown in the RegionServer's put metrics histogram never increases from 0 even though millions of such operations are made. Needless to say the latency for those operations are not measured either. The value of HBASE-5533 metrics are suspect given the client will batch put and delete ops like this.

I had a fix in progress but HBASE-6284 messed it up. Before, MultiAction processing in HRegionServer would distingush between puts and deletes and dispatch them separately. It was easy to account for the time for them. Now both puts and deletes are submitted in batch together as mutations.

Sub-Tasks

• Document HBase metrics: Closed