[jira] [Comment Edited] (ACCUMULO-882) Investigate making batch scanner and batch writer timeout idle threads

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

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

Keith Turner edited comment on ACCUMULO-882 at 11/28/12 2:25 PM:
-----------------------------------------------------------------

This was already fixed in trunk for the batch scanner.   A simple change was required for the batch writer.  In 1.4 threads will hang around forever if a batch scanner or batch writer is not closed.
                
      was (Author: kturner):
    This was already fixed in trunk for the batch scanner.   A simple change was required for the batch scanner.  In 1.4 threads will hang around forever if a batch scanner or batch writer is not closed.
                  
> Investigate making batch scanner and batch writer timeout idle threads
> ----------------------------------------------------------------------
>
>                 Key: ACCUMULO-882
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-882
>             Project: Accumulo
>          Issue Type: Improvement
>    Affects Versions: 1.4.0
>            Reporter: Keith Turner
>             Fix For: 1.5.0
>
>
> It may be possible to configure the thread pools used by batch scanner and batch writer such that threads idle out if the user forgets to call close.  User should still call close because the threads may continue doing work and using resources if they do not.    But in some cases making this change will help when the user does forget to close.

--
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: http://www.atlassian.com/software/jira