[jira] [Resolved] (HBASE-29233) Capture scan metrics at region level
[ https://issues.apache.org/jira/browse/HBASE-29233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viraj Jasani resolved HBASE-29233. -- Fix Version/s: 2.7.0 2.6.3 Resolution: Fixed > Capture scan metrics at region level > > > Key: HBASE-29233 > URL: https://issues.apache.org/jira/browse/HBASE-29233 > Project: HBase > Issue Type: Improvement > Components: Client, metrics >Reporter: Sanjeet Malhotra >Assignee: Sanjeet Malhotra >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0, 3.0.0-beta-2, 2.6.3 > > > In my company, we have a requirement that we would like to track scan metrics > for requests belonging to certain use cases at region level along with > getting info about where that region was hosted (RS) at the time of scan. > This will help us in knowing to which all regions and RS the request was > hitting and contribution of each region scan/RS in latency. Thus, I plan to > store region name and RS server name in scan metrics object only and capture > a list of Scan metrics (one per region scanned). > The capturing of scan metrics at this finer granularity can be "opt-in" per > Scan request and can be enabled via Scan attribute similar to how Scan > Metrics are enabled. > > I would like to backport this change to HBase 3 and HBase 2.6 and 2.5. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (HBASE-29233) Capture scan metrics at region level
[ https://issues.apache.org/jira/browse/HBASE-29233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viraj Jasani resolved HBASE-29233. -- Fix Version/s: (was: 2.7.0) (was: 2.5.12) (was: 2.6.4) Hadoop Flags: Reviewed Resolution: Fixed > Capture scan metrics at region level > > > Key: HBASE-29233 > URL: https://issues.apache.org/jira/browse/HBASE-29233 > Project: HBase > Issue Type: Improvement > Components: Client, metrics >Reporter: Sanjeet Malhotra >Assignee: Sanjeet Malhotra >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0-beta-2 > > > In my company, we have a requirement that we would like to track scan metrics > for requests belonging to certain use cases at region level along with > getting info about where that region was hosted (RS) at the time of scan. > This will help us in knowing to which all regions and RS the request was > hitting and contribution of each region scan/RS in latency. Thus, I plan to > store region name and RS server name in scan metrics object only and capture > a list of Scan metrics (one per region scanned). > The capturing of scan metrics at this finer granularity can be "opt-in" per > Scan request and can be enabled via Scan attribute similar to how Scan > Metrics are enabled. > > I would like to backport this change to HBase 3 and HBase 2.6 and 2.5. -- This message was sent by Atlassian Jira (v8.20.10#820010)
