[
https://issues.apache.org/jira/browse/ACCUMULO-487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13432157#comment-13432157
]
John Stoneham commented on ACCUMULO-487:
----------------------------------------
Would it be possible to have this fix backported to 1.3.x for those of us whose
systems haven't been upgraded to 1.4 yet? This leaks a lot of threads for our
use case and eventually runs the process out of threads.
> Batch Scanner can get stuck when external thread closes scanner
> ---------------------------------------------------------------
>
> Key: ACCUMULO-487
> URL: https://issues.apache.org/jira/browse/ACCUMULO-487
> 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:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
