Are you trying to stop the cluster or a node? If the former, then you can use control.sh to deactivate the cluster before stopping the nodes.
On Tue, May 8, 2018, 7:39 PM Randall Harmon <randall.har...@sizmek.com> wrote: > @dharvey - no, cluster is not deactivated. > > @anton - 26gb of data is under ignite data directory (not including WAL). > > I'd expect I can stop ignite server cleanly from unix shell. Do I really > have to run some java code to have persistence engine stop cleanly? > > When I send SIGINT or SIGTERM, it does stop, but then with the slow > startup. I understand why it would stop uncleanly if I was sending KILL > signal, but I'm not doing that. > > > > > On Tue, May 8, 2018 at 10:46 AM, akurbanov <antkr....@gmail.com> wrote: > >> Hello, >> >> You can call .close() method on Ignite instance or Ignition.stop. >> >> Could you also clarify, how many data was loaded between last checkpoint >> and >> node startup? >> >> Also, if possible, can you attach full node logs with -DIGNITE_QUIET=false >> or/and few consecutive thread dumps from recovering node during startup. >> >> Best regards, >> Anton >> >> >> >> >> >> -- >> Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >> > > Disclaimer The information contained in this communication from the sender is confidential. It is intended solely for use by the recipient and others authorized to receive it. If you are not the recipient, you are hereby notified that any disclosure, copying, distribution or taking action in relation of the contents of this information is strictly prohibited and may be unlawful. This email has been scanned for viruses and malware, and may have been automatically archived by Mimecast Ltd, an innovator in Software as a Service (SaaS) for business. Providing a safer and more useful place for your human generated data. Specializing in; Security, archiving and compliance. To find out more visit the Mimecast website.
