accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher Tubbs (JIRA)" <>
Subject [jira] [Updated] (ACCUMULO-607) BatchScanner sometimes logs error when closed
Date Tue, 18 Dec 2012 18:10:15 GMT


Christopher Tubbs updated ACCUMULO-607:

    Assignee: Keith Turner
> BatchScanner sometimes logs error when closed
> ---------------------------------------------
>                 Key: ACCUMULO-607
>                 URL:
>             Project: Accumulo
>          Issue Type: Bug
>          Components: client
>    Affects Versions: 1.4.0, 1.3.5
>            Reporter: Keith Turner
>            Assignee: Keith Turner
>             Fix For: 1.5.0
> 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

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

View raw message