You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Mikhail Petrov (Jira)" <ji...@apache.org> on 2020/11/23 16:06:00 UTC
[jira] [Commented] (IGNITE-13722) Ignite Spring Data: Ignite
resources are not closed properly when closing Spring context.
[ https://issues.apache.org/jira/browse/IGNITE-13722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17237456#comment-17237456 ]
Mikhail Petrov commented on IGNITE-13722:
-----------------------------------------
TC run results - [https://ci.ignite.apache.org/viewLog.html?buildId=5752711&buildTypeId=Tests_IgniteExtensions_Build]
> Ignite Spring Data: Ignite resources are not closed properly when closing Spring context.
> -----------------------------------------------------------------------------------------
>
> Key: IGNITE-13722
> URL: https://issues.apache.org/jira/browse/IGNITE-13722
> Project: Ignite
> Issue Type: Improvement
> Reporter: Mikhail Petrov
> Assignee: Mikhail Petrov
> Priority: Major
>
> It's needed to close Ignite thin/thick client that is used by Spring Data for accessing the Ignite cluster when closing Spring context.
> Currently, if Ignite/ClientConfiguration is used to configure Ignite cluster access for a repository (see RepositoryConfig), instances of Ignite/IgniteClient remains unclosed after the close of Spring context.
> To solve this issue it's proposed to move management of Ignite instances needed for accessing the cluster by Spring Data to separate configurable bean. It will be auto-registered by Spring Data and will close all Ignite resources when closing the Spring context.
>
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)