You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ignite.apache.org by "Vladimir Ozerov (JIRA)" <ji...@apache.org> on 2015/09/14 14:33:46 UTC

[jira] [Created] (IGNITE-1478) Service cannot be used on remote node immediately after deployment.

Vladimir Ozerov created IGNITE-1478:
---------------------------------------

             Summary: Service cannot be used on remote node immediately after deployment.
                 Key: IGNITE-1478
                 URL: https://issues.apache.org/jira/browse/IGNITE-1478
             Project: Ignite
          Issue Type: Task
          Components: cache
    Affects Versions: 1.1.4
            Reporter: Vladimir Ozerov
            Priority: Critical
             Fix For: ignite-1.5


Consider the following scenario:
1) Two nodes: A and B.
2) Node A deploys cluster-wide service through IgniteServices.deploy();
3) Once we exited deploy() method we are trying to get the service on the node B in any way (invoke it, get proxy, get descriptor, whatever). 

Step 3 might fail. This happens because GridServiceProcessor.AssignmentListener is not notified synchronously when service cache is update in transaction. 
As a result, transacion ends, node A informs us about successful service deployment, but it is still not usable on remote nodes.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)