[
https://issues.apache.org/jira/browse/ACCUMULO-607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Josh Elser updated ACCUMULO-607:
--------------------------------
Fix Version/s: (was: 1.7.0)
1.7.1
1.8.0
> BatchScanner sometimes logs error when closed
> ---------------------------------------------
>
> Key: ACCUMULO-607
> URL: https://issues.apache.org/jira/browse/ACCUMULO-607
> Project: Accumulo
> Issue Type: Bug
> Components: client
> Affects Versions: 1.3.5, 1.4.0
> Reporter: Keith Turner
> Fix For: 1.5.3, 1.6.3, 1.8.0, 1.7.1
>
>
> The batch scanner has a threadpool. When the batch scanner is closed it
> calls shutdownNow() on this threadpool, which interrupts all of the threads.
> If a user does not read all data from a batch scanner and calls close, thens
> its likely that the background threads are still busy and will be
> interrupted. This is a normal course of business, so there is no need to log
> an exception for these interrupted excpetions. Some places in the code do
> log an error when these exceptions occur.
> One place is where the background code calls UtilWaitThread.sleep(). There
> may be other places.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
