accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Keith Turner (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-4643) Allow iterators to interrupt themselves
Date Tue, 30 May 2017 18:51:04 GMT


Keith Turner commented on ACCUMULO-4643:

The behaviour is expected to be identical to when an iterator is torn down because the buffer
is filled, or the timeout is reached.

There is currently isolation of data sources when computing a single key/value.  If using
this feature, the computation of single key/value could be done using different data sources.
 That's a big difference.

> Allow iterators to interrupt themselves
> ---------------------------------------
>                 Key: ACCUMULO-4643
>                 URL:
>             Project: Accumulo
>          Issue Type: Improvement
>          Components: tserver
>    Affects Versions: 1.8.1, 2.0.0
>            Reporter: Ivan Bella
>            Assignee: Ivan Bella
>              Labels: features
>             Fix For: 2.0.0
>          Time Spent: 6h 10m
>  Remaining Estimate: 0h
> The idea here is to allow an iterator stack to send back a special key or throw a special
exception which will allow the tablet server to tear down the scan to be rebuilt later.  This
is to handle the case where an iterator is doing a lot of work without returning results to
avoid starving out other scans.
> There are two thoughts on how to do this:
> 1) A special "interrupt" key is returned from the getTopKey call that is detected in
the Tablet.nextBatch call, is not added to the results, but is used to add an unfinished range
and results in the remaining ranges to be deemed unfinished.
> 2) An special exception is thrown from the next or seek call that included the key of
the current position, and the same actions are taken as in 1).

This message was sent by Atlassian JIRA

View raw message