[
https://issues.apache.org/jira/browse/IGNITE-4740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Karachentsev updated IGNITE-4740:
----------------------------------------
Description:
In case of concurrent service cancel and discovery event, for example, applying
continuous query, may cause double service deploy/undeploy.
Fix should consist in filtering such DiscoveryCustomEvent in
GridServiceProcessor.TopologyListener.
was:
In case of concurrent service cancel and discovery event, for example, applying
continuous query, may cause double init() and execute() service method
invocation.
Fix should consist at least in filtering such DiscoveryCustomEvent in
GridServiceProcessor.TopologyListener.
The best solution is guarantee that despite of any discovery event service
won't be intialized more than once.
> Service could be deployed twice on concurrent cancel and discovery event
> ------------------------------------------------------------------------
>
> Key: IGNITE-4740
> URL: https://issues.apache.org/jira/browse/IGNITE-4740
> Project: Ignite
> Issue Type: Bug
> Components: managed services
> Affects Versions: 1.8
> Reporter: Dmitry Karachentsev
> Assignee: Dmitry Karachentsev
> Fix For: 2.0
>
>
> In case of concurrent service cancel and discovery event, for example,
> applying continuous query, may cause double service deploy/undeploy.
> Fix should consist in filtering such DiscoveryCustomEvent in
> GridServiceProcessor.TopologyListener.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
