Yeah, that is wha I thought. But Ignite is wired with Spring so that would mean restarting the whole ApplicationContext.
Ralph > On Jan 18, 2018, at 10:37 AM, ilya.kasnacheev <ilya.kasnach...@gmail.com> > wrote: > > Hello Ralph! > > I imagine if your Ignite is running inside a web container, it is the > responsibility of your code to check its status and when it disconnects, > notify balancer that current node can't handle requests and then try to > re-join topology with a new instance of Ignite. > > Regards, > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
