[ https://issues.apache.org/jira/browse/HBASE-13054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14330191#comment-14330191 ]
Hudson commented on HBASE-13054: -------------------------------- FAILURE: Integrated in HBase-0.98-on-Hadoop-1.1 #824 (See [https://builds.apache.org/job/HBase-0.98-on-Hadoop-1.1/824/]) HBASE-13054 Provide more tracing information for locking/latching events.(Rajeshbabu) (rajeshbabu: rev 137d5e62dff459cf194c43bf9573aa7dd5f24330) * hbase-server/src/main/java/org/apache/hadoop/hbase/io/hfile/HFileReaderV2.java * hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/HRegion.java * hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/MemStore.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)