You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@accumulo.apache.org by "Keith Turner (JIRA)" <ji...@apache.org> on 2013/01/14 23:32:12 UTC

[jira] [Resolved] (ACCUMULO-728) Leaks a BatchScanner thread pool for each BatchDeleter

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

Keith Turner resolved ACCUMULO-728.
-----------------------------------

       Resolution: Fixed
    Fix Version/s:     (was: 1.5.0)
                   1.4.0
    
> Leaks a BatchScanner thread pool for each BatchDeleter
> ------------------------------------------------------
>
>                 Key: ACCUMULO-728
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-728
>             Project: Accumulo
>          Issue Type: Bug
>          Components: client
>    Affects Versions: 1.3.6, 1.3.5, 1.3.7
>            Reporter: John Stoneham
>            Assignee: Keith Turner
>             Fix For: 1.4.0
>
>
> Each BatchDeleter (i.e., TabletServerBatchDeleter) causes a BatchScanner thread to leak. This is because TabletServerBatchDeleter extends TabletServerBatchReader which opens a thread pool on construction but no close() method is offered on the BatchDeleter interface.
> Workaround: downcast BatchDeleter to either BatchScanner or TabletServerBatchDeleter, then call close().
> It appears the close() method is available on BatchDeleter from 1.4 forward, but this still affects 1.3 series users (which is why I'm documenting it).
> Since BatchDeleter is a one-off class - call delete() and forget - it might make sense for it to close itself instead when complete.

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