[jira] [Updated] (HBASE-13054) Provide more tracing information for locking/latching events.
[ https://issues.apache.org/jira/browse/HBASE-13054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajeshbabu Chintaguntla updated HBASE-13054: Description: 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. (was: 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's better to provide more information for such events.) > 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 > > > 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)
[jira] [Updated] (HBASE-13054) Provide more tracing information for locking/latching events.
[ https://issues.apache.org/jira/browse/HBASE-13054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajeshbabu Chintaguntla updated HBASE-13054: Attachment: HBASE-13054.patch Here is the patch just adding tracing in few places. 1) While getting a row lock possible lock contention under heavy load so just added trace info there. 2) trace info for block cache hit and scan request going through mem store. Mostly there should not be much lock contention issues because shared locks are getting used in all most all the places. That's why not adding much tracing info. > 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 > > Attachments: HBASE-13054.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)
[jira] [Updated] (HBASE-13054) Provide more tracing information for locking/latching events.
[ https://issues.apache.org/jira/browse/HBASE-13054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajeshbabu Chintaguntla updated HBASE-13054: Fix Version/s: 0.98.11 Hadoop Flags: Reviewed Status: Patch Available (was: Open) > 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_v2.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)
[jira] [Updated] (HBASE-13054) Provide more tracing information for locking/latching events.
[ https://issues.apache.org/jira/browse/HBASE-13054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajeshbabu Chintaguntla updated HBASE-13054: Attachment: HBASE-13054_v2.patch Thanks for review [~apurtell]. Here is the patch adding Trace.isTracing check in HRegion. > 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 > > Attachments: HBASE-13054.patch, HBASE-13054_v2.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)
[jira] [Updated] (HBASE-13054) Provide more tracing information for locking/latching events.
[ https://issues.apache.org/jira/browse/HBASE-13054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajeshbabu Chintaguntla updated HBASE-13054: Attachment: HBASE-13054_v3.patch Thanks for review [~eclark]. Here is the patch addressing the comments. If it's ok I will commit. > 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_v2.patch, > HBASE-13054_v3.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)
[jira] [Updated] (HBASE-13054) Provide more tracing information for locking/latching events.
[ https://issues.apache.org/jira/browse/HBASE-13054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajeshbabu Chintaguntla updated HBASE-13054: Attachment: HBASE-13056_branch-1.patch Patch for branch-1 > 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_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)
[jira] [Updated] (HBASE-13054) Provide more tracing information for locking/latching events.
[ https://issues.apache.org/jira/browse/HBASE-13054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajeshbabu Chintaguntla updated HBASE-13054: Attachment: HBASE-13054_0.98.patch patch for 0.98. I will commit shortly. > 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)
[jira] [Updated] (HBASE-13054) Provide more tracing information for locking/latching events.
[ https://issues.apache.org/jira/browse/HBASE-13054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajeshbabu Chintaguntla updated HBASE-13054: Resolution: Fixed Status: Resolved (was: Patch Available) Pushed to 0.98+ branches. Thanks for review [~apurtell],[~eclark]. > 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)
