You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Sergey Uttsel (Jira)" <ji...@apache.org> on 2022/10/31 09:03:00 UTC
[jira] [Assigned] (IGNITE-17899) Properly stop resources in TableManager
[ https://issues.apache.org/jira/browse/IGNITE-17899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sergey Uttsel reassigned IGNITE-17899:
--------------------------------------
Assignee: Sergey Uttsel
> Properly stop resources in TableManager
> ---------------------------------------
>
> Key: IGNITE-17899
> URL: https://issues.apache.org/jira/browse/IGNITE-17899
> Project: Ignite
> Issue Type: Task
> Reporter: Mirza Aliev
> Assignee: Sergey Uttsel
> Priority: Major
> Labels: ignite-3
>
> It's required to add sort of stopAll logic that will try to stop all resources even if some of them throws an exception on stop in {{org.apache.ignite.internal.table.distributed.TableManager#cleanUpTablesResources}}. Currently, if some components throws exception during `TableManager` stop, other components won't be stopped.
> I'd rather use something similar to {{org.apache.ignite.internal.util.IgniteUtils#closeAll(java.util.Collection<? extends java.lang.AutoCloseable>)}}.
> Also `MvTableStorage` must be `AutoClosable`
--
This message was sent by Atlassian Jira
(v8.20.10#820010)