Hello Chris? Are you using ignite-spring bindings? There's a problem with initialization lifecycle that will be fixed in the next release: https://issues.apache.org/jira/browse/IGNITE-6555
If that is the case, as a workaround you can put Ignite in a dedicated context and only start it at the last moment when the parent context is up and running, as described here: https://stackoverflow.com/questions/44696908/spring-make-serveltdispatcher-context-await-until-another-context-finish-loadin (It will not be serviet context as in that example but a context containing Ignite) If it is your own code starting Ignite, it is your duty to start it at appropriate time, using the same workaround as an example. Listen to Spring events, run Ignite when ready. Regards, -- Ilya Kasnacheev 2017-11-16 21:24 GMT+03:00 Chris Berry <chriswbe...@gmail.com>: > No. There are things in the general application that are not yet > initialized. > It is essentially a chicken-and-egg problem. > I need to start Ignite, and do various other things before I am ready to > take load. > But as soon as Ignite is started -- it starts to take ComputeJobs. > > We really need a way to tell Ignite that the app is ready to accept > ComputJobs. > Instead of it assuming that once it is started, then it must be ready, by > default. > > Basically, a gate. > > Thanks, > -- Chris > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
