hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-5980) Scanner responses from RS should include metrics on rows/KVs filtered
Date Thu, 21 May 2015 18:17:18 GMT

     [ https://issues.apache.org/jira/browse/HBASE-5980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

stack updated HBASE-5980:
       Resolution: Fixed
    Fix Version/s: 1.2.0
     Release Note: 
Adds scan metrics to the result. In the shell, set the ALL_METRICS attribute to true on your
scan to see dump of metrics after results (see the scan help for examples).

If you would prefer to see only a subset of the metrics, the METRICS array can be defined
to include the names of only the metrics you care about.
     Hadoop Flags: Reviewed
           Status: Resolved  (was: Patch Available)

Pushed to branch-1 and master.

Nice facility that gives insight on what is going on server-side.

It is off by default so should have no impact on scan perf.

Thanks [~jonathan.lawlor]

> Scanner responses from RS should include metrics on rows/KVs filtered
> ---------------------------------------------------------------------
>                 Key: HBASE-5980
>                 URL: https://issues.apache.org/jira/browse/HBASE-5980
>             Project: HBase
>          Issue Type: Improvement
>          Components: Client, metrics, Operability, regionserver
>    Affects Versions: 0.95.2
>            Reporter: Todd Lipcon
>            Assignee: Jonathan Lawlor
>            Priority: Minor
>             Fix For: 2.0.0, 1.2.0
>         Attachments: 5980v5.master.txt, 5980v5.txt, 5980v5.txt, 5980v5.txt, 5980v5.txt,
HBASE-5980-branch-1.patch, HBASE-5980-v1.patch, HBASE-5980-v2.patch, HBASE-5980-v2.patch,
HBASE-5980-v3.patch, HBASE-5980-v4.patch
> Currently it's difficult to know, when issuing a filter, what percentage of rows were
skipped by that filter. We should expose some basic counters back to the client scanner object.
For example:
> - number of rows filtered by row key alone (filterRowKey())
> - number of times each filter response was returned by filterKeyValue() - corresponding
to Filter.ReturnCode
> What would be slickest is if this could actually return a tree of counters for cases
where FilterList or other combining filters are used. But a top-level is a good start.

This message was sent by Atlassian JIRA

View raw message