[ 
https://issues.apache.org/jira/browse/IGNITE-8279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Denis Mekhanikov updated IGNITE-8279:
-------------------------------------
    Description: 
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 in service 
cache changes.

Find attached test, reproducing this problem.

  was:
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.


> 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
>            Priority: Major
>             Fix For: 2.6
>
>         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 in service 
> cache changes.
> Find attached test, reproducing this problem.



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

Reply via email to