Hi Arthi, In current implementation, node instance (i.e. Ignite instance) can not be shared between different processes. Can you describe your use case a bit more? Which start up time would be acceptable in your case? Are you starting client node on the startup of the application or are you starting it whenever you need to make requests?
Best Regards, Igor On Mon, May 16, 2016 at 7:05 AM, arthi <arthi.kasturirangan...@nielsen.com> wrote: > Hi Igor, > > Is this possible? > > My C++ client application will need to create multiple requests to access > the data grid for executing SQL queries. > > There could be 400-500 concurrent requests on high load. If I could re-use > the same client node instance (or may balance across a set of client node > instances), my topology will be stable. I will not be altering the topology > for every incoming request for a new client. The time taken to join the > cluster as a client takes 4-5 seconds, and on concurrent load, even greater > (10-20 seconds). > > will shared memory help? Can you please provide sample code to do this? > > Please advice. > > Thanks, > Arthi > > > > -- > View this message in context: > http://apache-ignite-users.70518.x6.nabble.com/Get-client-node-instance-tp4897p4946.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com. >
