Hello! I guess what you are trying to say is that Ignite will prefer local service deployment instead of distributing requests to all distributed nodes.
This is highlighted in its documentation: * Gets a remote handle on the service. If service is available locally, * then local instance is returned, otherwise, a remote proxy is dynamically * created and provided for the specified service. I guess you can try using ignite.services(random server node).serviceProxy()... Regards, -- Ilya Kasnacheev пт, 14 авг. 2020 г. в 02:44, satyan <chellasam...@zohocorp.com>: > Hi, I am new to ignite. I have a requirement and I don't know how to > achieve > it through Ignite. > > My usecase: > > Suppose if I have 3 servers, one among them will act as a leader and will > co-ordinate all the internal service requests. > The requests should get executed either in the same server(leader) or any > other servers. > For this I have embedded a Ignite leader node through service proxy > instance, all the requests are getting executed in the same server itself, > distribution is not happening. > But If I create a client & a server node instance in t server node instance > in all the 3 servers and have formed a cluster. > If I execute the service requests from the leader node and then execute the > service requests through the client, the requests are getting distributed > across other nodes. > Is this client node instance required for service distribution to happen? > Please help. > _ > > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
