Hi Denis, Would this be better to target 2.5? It seems like a significant regression...
Thanks, Raymond. Sent from my iPhone > On 17/04/2018, at 1:46 AM, Denis Mekhanikov (JIRA) <j...@apache.org> wrote: > > Denis Mekhanikov created IGNITE-8279: > ---------------------------------------- > > Summary: 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 > Affects Versions: 2.4 > Reporter: Denis Mekhanikov > Assignee: Denis Mekhanikov > Fix For: 2.6 > Attachments: ServiceDeploymentAfterDeactivationTest.java > > When this 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 in service > cache changes. > > Find attached test, reproducing this problem. > > > > -- > This message was sent by Atlassian JIRA > (v7.6.3#76005)
