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

Posted to notifications@accumulo.apache.org by "Christopher Tubbs (Jira)" <ji...@apache.org> on 2020/10/28 23:08:00 UTC

[jira] [Resolved] (ACCUMULO-3740) Investigate split/assignment threadpool shutdown

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

Christopher Tubbs resolved ACCUMULO-3740.
-----------------------------------------
    Resolution: Abandoned

Closing this stale issue. If this is still a problem, please open a new issue or PR at https://github.com/apache/accumulo

> Investigate split/assignment threadpool shutdown
> ------------------------------------------------
>
>                 Key: ACCUMULO-3740
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-3740
>             Project: Accumulo
>          Issue Type: Task
>            Reporter: Christopher Tubbs
>            Priority: Major
>
> Commit a194c0b00b7a927e938da72350916f30b0a0707d for ACCUMULO-3204 removed some unused code in the TabletServerResourceManager.
> It is curious why this code was unused, because it seemed like it may have needed to be used.
> The methods were named:
> * stopSplits
> * stopNormalAssignments
> * stopMetadataAssignments
> The underlying thread pools these methods were supposed to shut down do not appear to be stopped anywhere else.
> We should investigate whether it is a problem that these thread pools are never shut down, and if it is, reintroduce the deleted code, with additional code to appropriately call it.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)