ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Valentin Kulichenko (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-8436) Executor service for services does not shutdown properly
Date Tue, 08 May 2018 00:06:00 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-8436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16466644#comment-16466644
] 

Valentin Kulichenko commented on IGNITE-8436:
---------------------------------------------

[~prabhat], I don't think there are tests that cover this. Could you please create one? I
would just check that there are no Ignite threads and/or thread pools are running after node
stop. 

> Executor service for services does not shutdown properly
> --------------------------------------------------------
>
>                 Key: IGNITE-8436
>                 URL: https://issues.apache.org/jira/browse/IGNITE-8436
>             Project: Ignite
>          Issue Type: Bug
>          Components: managed services
>            Reporter: Maxim Muzafarov
>            Assignee: Prabhat Ranjan
>            Priority: Major
>              Labels: newbie
>             Fix For: 2.6
>
>
> Issue [IGNITE-4802|https://issues.apache.org/jira/browse/IGNITE-4802] introduces us separete
thread pool for services execution.
> {{IgniteEx}} class defines a factory for the main Ignite API. It controls Grid life cycle
and allows listening for grid events. 
> As cotributor, you should ensure that execution pool shutdowns properly and provide fix
if needed in case stop grid instance method call occurs.
> {code:java|title=IgniteEx.java|borderStyle=solid}
> /** Executor service for services. */
> private ThreadPoolExecutor svcExecSvc;
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message