[
https://issues.apache.org/jira/browse/ACCUMULO-728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christopher Tubbs updated ACCUMULO-728:
---------------------------------------
Affects Version/s: (was: 1.3.7)
> 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.5, 1.3.6
> 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
