[jira] [Updated] (ACCUMULO-607) BatchScanner sometimes logs error when closed

["Keith Turner (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/ACCUMULO-607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Keith Turner updated ACCUMULO-607:
----------------------------------

    Description: 
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.

  was:
The batch scanner has a threadpool.  When the batch scanner is closed it calls shutdownNow() on this threadpool, which interrupts all of the thread.  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 not 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 there the background code call UtilWaitThread.sleep().  There may be other places.

    
> 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.4.0, 1.3.5
>            Reporter: Keith Turner
>            Assignee: Billie Rinaldi
>             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 places.

--
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