[
https://issues.apache.org/jira/browse/HBASE-4926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack resolved HBASE-4926.
--------------------------
Resolution: Won't Fix
Resovling old idea not acted upon. Scan metrics does some of this.
> DebugFilter; counts how many KVs skipped before result found, counts
> storefiles we tripped over
> -----------------------------------------------------------------------------------------------
>
> Key: HBASE-4926
> URL: https://issues.apache.org/jira/browse/HBASE-4926
> Project: HBase
> Issue Type: Task
> Reporter: stack
>
> I'm not sure this possible but chatting w/ J-D after he finished helping a
> crew who had a slow scan, we need ways to help folks figure out why stuff is
> slow on the server side. In this case, the user had a region that had gigs
> of deletes in it that had to be skipped before the scanner got to a value to
> return so scans looked slow though working 'correctly'. If the user could
> enable a DebugFilter than did counts of what Scans were skipping and size of
> data skipped among other things, it might help w/ the situation above -- and
> perhaps with others (What else could we count in a filter?)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
