accumulo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Stoneham (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-487) Batch Scanner can get stuck when external thread closes scanner
Date Thu, 09 Aug 2012 21:45:19 GMT


John Stoneham commented on ACCUMULO-487:

Nevermind. This is a different resource leak I'll file later if it hasn't been fixed on trunk.
> Batch Scanner can get stuck when external thread closes scanner
> ---------------------------------------------------------------
>                 Key: ACCUMULO-487
>                 URL:
>             Project: Accumulo
>          Issue Type: Bug
>          Components: client
>    Affects Versions: 1.4.0, 1.3.5
>            Reporter: John Vines
>            Assignee: Keith Turner
>              Labels: newbie
>             Fix For: 1.5.0, 1.4.1
> Scenario- client is using batch scanner to run queries with complex server side iterators.
They run long. User has external thread which determines thread is running long, so that thread
calls close on the batch scanner. Query threads exit nicely, but there is a thread which is
constantly polling an internal queue. It only breaks out of that loop if there is a next key
or an error thrown. If neither occur, it continues to poll. We should probably have an exit
condition get set on close() which is used in that query loop.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message