You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Denis Mekhanikov (JIRA)" <ji...@apache.org> on 2018/08/29 08:15:00 UTC
[jira] [Updated] (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:all-tabpanel ]
Denis Mekhanikov updated IGNITE-8279:
-------------------------------------
Fix Version/s: (was: 2.7)
2.8
> 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
(v7.6.3#76005)