[
https://issues.apache.org/jira/browse/HBASE-13054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14330097#comment-14330097
]
Hudson commented on HBASE-13054:
--------------------------------
FAILURE: Integrated in HBase-TRUNK #6157 (See
[https://builds.apache.org/job/HBase-TRUNK/6157/])
HBASE-13054 Provide more tracing information for locking/latching
events.(Rajeshbabu) (rajeshbabu: rev 7792dee0c36de9b3108ebf60f6394f2d7e9a1b9f)
*
hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/DefaultMemStore.java
* hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/HRegion.java
* hbase-server/src/main/java/org/apache/hadoop/hbase/io/hfile/HFileReaderV2.java
> Provide more tracing information for locking/latching events.
> -------------------------------------------------------------
>
> Key: HBASE-13054
> URL: https://issues.apache.org/jira/browse/HBASE-13054
> Project: HBase
> Issue Type: Improvement
> Reporter: Rajeshbabu Chintaguntla
> Assignee: Rajeshbabu Chintaguntla
> Fix For: 2.0.0, 1.0.1, 1.1.0, 0.98.11
>
> Attachments: HBASE-13054.patch, HBASE-13054_0.98.patch,
> HBASE-13054_v2.patch, HBASE-13054_v3.patch, HBASE-13056_branch-1.patch
>
>
> Currently not much tracing information available for locking and latching
> events like row level locking during do mini batch mutations, region level
> locking during flush, close and so on. It will be better to add the trace
> information for such events so that it will be useful for finding time spent
> on locking and waiting time on locks while analyzing performance issues in
> queries using trace information.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
