accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-607) BatchScanner sometimes logs error when closed
Date Sat, 10 May 2014 22:12:55 GMT

    [ https://issues.apache.org/jira/browse/ACCUMULO-607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13993060#comment-13993060
] 

Josh Elser commented on ACCUMULO-607:
-------------------------------------

[~kturner], are you planning on working on this? It would be good to look into this and try
to get it suppressed to avoid user confusion about the exception being logged.

> 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
>            Assignee: Keith Turner
>             Fix For: 1.5.2, 1.6.1, 1.7.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 was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message