My alternative solution didn't work. We need a solution where we can get the worker nodes to obtain configuration form the server node (client only) via URL. This allows us to easily deploy worker nodes across the network with little copying/updating of the Ignite configuration.
Client Only mode waits for a non-client to connect to the cluster, this prevents out Spring configuration from completing whilst it polls making http requests time out. My work-around for another issue is to deploy the Ignite configuration locally for each worker node. Version 1.0.6 did not have this restriction in place. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Client-Only-Server-that-doesn-t-rely-on-Nodes-on-intialisation-tp788p795.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
