Thanks Dmitriy, That did the trick. The only warning left is
WAL segment tail reached. which based on your answer to a different post should be INFO not WARN. Cheers, Jorg Jorg Janke - www.accorto.com - (650) 227-3271 On Tue, Apr 23, 2019 at 2:54 PM Dmitriy Pavlov <[email protected]> wrote: > Hi, > > Just Ignition.stop(true); should be enough to wait till checkpoint ends. > So it could be just one call to this method without anything else. > > If you did a prior call to ignite.close() this is equal to > Ignition.stop(false) and this cause Ignite node to stop without waiting for > checkpoint to finish. In that case, further calls have no effect. > > In any case, this warning says that it may require a longer time to > restore memory during start-up, but not something that is dangerous for > data. > > Sincerely, > Dmitriy Pavlov > > вт, 23 апр. 2019 г. в 22:58, Jorg Janke <[email protected]>: > >> We try to shut down Ignite properly via: >> >> m_ignite.close(); // Ignite.close() >> m_ignite.executorService().shutdown(); >> Ignition.stop(true); >> >> but still get: >> >> WARN: Ignite node stopped in the middle of checkpoint. Will restore >> memory state and finish checkpoint on node start. >> >> What is the recommended way to stop/shut down an (embedded) ignite >> instance? >> >> Thanks! >> Jorg >> >> Jorg Janke - www.accorto.com - (650) 227-3271 >> >
