[ https://issues.apache.org/jira/browse/HBASE-5978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13281228#comment-13281228 ]
Alex Newman commented on HBASE-5978: ------------------------------------ I assume you want this to return before any exception is thrown? > Scanner next() calls should return after a configurable time threshold > regardless of number of accumulated rows > --------------------------------------------------------------------------------------------------------------- > > Key: HBASE-5978 > URL: https://issues.apache.org/jira/browse/HBASE-5978 > Project: HBase > Issue Type: Improvement > Components: client, regionserver > Affects Versions: 0.90.7, 0.92.1 > Reporter: Todd Lipcon > > Currently if you pass a very restrictive filter to a scanner, along with a > high caching value, you will end up causing RPC timeouts, lease exceptions, > etc. Although this is a poor configuration and easy to work around by > lowering caching, HBase should be resilient to a badly chosen caching value. > As such, the scanner next() call should record the elapsed time, and after > some number of seconds have passed, return any accumulated rows regardless of > the caching value. This prevents the calls from starving out other threads or > region operations. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira