You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Maxim Muzafarov (Jira)" <ji...@apache.org> on 2019/10/08 11:12:00 UTC
[jira] [Commented] (IGNITE-8279) Clients can't operate on services
after deactivation
[ https://issues.apache.org/jira/browse/IGNITE-8279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16946719#comment-16946719 ]
Maxim Muzafarov commented on IGNITE-8279:
-----------------------------------------
[~pvinokurov]
Hello! Any updates on this issue?
> Clients can't operate on services after deactivation
> ----------------------------------------------------
>
> Key: IGNITE-8279
> URL: https://issues.apache.org/jira/browse/IGNITE-8279
> Project: Ignite
> Issue Type: Bug
> Components: managed services
> Affects Versions: 2.4
> Reporter: Denis Mekhanikov
> Assignee: Pavel Vinokurov
> Priority: Major
> Fix For: 2.8
>
> Attachments: ServiceDeploymentAfterDeactivationTest.java
>
>
> When a cluster gets deactivated and activated back again, clients become incapable of service deployment. Calls to {{IgniteService.deploy*}} methods hang indefinitely, and no services are getting deployed to these clients.
> After deactivation, {{ServiceEntriesListener}} stops being invoked on service cache changes.
> Find attached test, reproducing this problem.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)