[jira] [Created] (IGNITE-8279) Clients can't operate on services after deactivation

[Anton Vinogradov (Jira)]

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)

[Raymond Wilson]

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) <[hidden email]> 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)

[Dmitriy Pavlov]

Hi Raymond,

I thought 2.5 is already freezed.
Several days remained to release (vote), so it is not likely this issue can
be done.

Probably Denis M. or Andrey G. could correct me if I'm wrong.

Sincerely,
Dmitriy Pavlov

пн, 16 апр. 2018 г. в 21:52, Raymond Wilson <[hidden email]>:

> 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) <[hidden email]>
> 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)
>

[Denis Mekhanikov]

Raymond,

The issue here is that client connections lose subscriptions to events,
related to service deployment.
So, clients can deploy services to other nodes, but they don't return
execution from *IgniteServices#deploy* *methods.

The workaround here is to restart clients, that were present in the cluster
during deactivation.

We've been having this issue since activation feature was introduced. This
is not some recent regression. Nobody complained about it, so I don't think
it's critical.
It will be fixed in 2.6, since patches are already not accepted into 2.5

Denis

вт, 17 апр. 2018 г. в 15:52, Dmitry Pavlov <[hidden email]>:

> Hi Raymond,
>
> I thought 2.5 is already freezed.
> Several days remained to release (vote), so it is not likely this issue can
> be done.
>
> Probably Denis M. or Andrey G. could correct me if I'm wrong.
>
> Sincerely,
> Dmitriy Pavlov
>
> пн, 16 апр. 2018 г. в 21:52, Raymond Wilson <[hidden email]>:
>
> > 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) <[hidden email]>
> > 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)
> >
>

[Raymond Wilson]

Thanks for the extra detail Denis. I agree, it is not critical for 2.5 given
the workaround you describe.

-----Original Message-----
From: Denis Mekhanikov [mailto:[hidden email]]
Sent: Wednesday, April 18, 2018 6:44 AM
To: [hidden email]
Subject: Re: [jira] [Created] (IGNITE-8279) Clients can't operate on
services after deactivation

Raymond,

The issue here is that client connections lose subscriptions to events,
related to service deployment.
So, clients can deploy services to other nodes, but they don't return
execution from *IgniteServices#deploy* *methods.

The workaround here is to restart clients, that were present in the cluster
during deactivation.

We've been having this issue since activation feature was introduced. This
is not some recent regression. Nobody complained about it, so I don't think
it's critical.
It will be fixed in 2.6, since patches are already not accepted into 2.5

Denis

вт, 17 апр. 2018 г. в 15:52, Dmitry Pavlov <[hidden email]>:

> Hi Raymond,
>
> I thought 2.5 is already freezed.
> Several days remained to release (vote), so it is not likely this
> issue can be done.
>
> Probably Denis M. or Andrey G. could correct me if I'm wrong.
>
> Sincerely,
> Dmitriy Pavlov
>
> пн, 16 апр. 2018 г. в 21:52, Raymond Wilson <[hidden email]>:
>
> > 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)
> > > <[hidden email]>
> > 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)
> >
>