Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Duplicate
-
0.90.7, 0.92.1
-
None
-
None
Description
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.