[
https://issues.apache.org/jira/browse/HBASE-4926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13445711#comment-13445711
]
Jesse Yates commented on HBASE-4926:
------------------------------------
@stack but wouldn't this make more sense as part of the information you get
back from a regular operation? Maybe you turn on a flag in the client and it
starts dumping data about scans, transparently to everything else. I could see
that as the DebugFilter, but it would be nice to make that pretty much
transparent to the existing operation (like the tracing is).
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
