[ 
https://issues.apache.org/jira/browse/HBASE-6377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13413674#comment-13413674
 ] 

Hudson commented on HBASE-6377:
-------------------------------

Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #92 (See 
[https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/92/])
    HBASE-6377. HBASE-5533 metrics miss all operations submitted via MultiAction

Committed 6377-trunk-remove-get-put-delete-histograms.patch (Revision 1361026)

     Result = FAILURE
apurtell : 
Files : 
* 
/hbase/trunk/hbase-server/src/main/jamon/org/apache/hadoop/hbase/tmpl/regionserver/ServerMetricsTmpl.jamon
* 
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/metrics/RegionServerMetrics.java

                
> HBASE-5533 metrics miss all operations submitted via MultiAction
> ----------------------------------------------------------------
>
>                 Key: HBASE-6377
>                 URL: https://issues.apache.org/jira/browse/HBASE-6377
>             Project: HBase
>          Issue Type: Bug
>          Components: metrics, regionserver
>    Affects Versions: 0.96.0, 0.94.1
>            Reporter: Andrew Purtell
>            Assignee: Andrew Purtell
>             Fix For: 0.96.0, 0.94.1
>
>         Attachments: 6377-0.94-remove-get-put-delete-histograms.patch, 
> 6377-0.94.patch, 6377-trunk-remove-get-put-delete-histograms.patch, 
> 6377-trunk-simple.patch, 6377.patch
>
>
> 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.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to