hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Lawlor (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (HBASE-5978) Scanner next() calls should return after a configurable time threshold regardless of number of accumulated rows
Date Wed, 08 Apr 2015 19:27:12 GMT

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

Jonathan Lawlor resolved HBASE-5978.
------------------------------------
    Resolution: Duplicate

Resolving as duplicate as this issue seems to be the same as HBASE-13090.

> 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 was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message