[
https://issues.apache.org/jira/browse/IGNITE-8279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16946913#comment-16946913
]
Denis Mekhanikov commented on IGNITE-8279:
------------------------------------------
[~mmuzaf] this issue is not reproduced in the new implementation of the service
grid, that was done under the following IEP:
[https://cwiki.apache.org/confluence/display/IGNITE/IEP-17%3A+Oil+Change+in+Service+Grid]
The issue appears only when {{IGNITE_EVENT_DRIVEN_SERVICE_PROCESSOR_ENABLED}}
environment property is set to false.
I guess, we can resolve this issue as "won't fix".
> 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)
