I guess, basically you are trying to see, which java process is stopping at last. If this is the last process, you have to deactivate the cluster, or else just disconnect. You might be getting the above error as one node is trying to disconnect and another node is trying to deactivate.
In order to resolve this, you can try out a centralised approach to check how many processes are running. For instance, zookeeper. If a new node is spawning, we ideally add a Z node in the zookeeper and remove it if it gets deleted. If you don't want to use a zookeeper, you can have another approach like files for different processes in a centralised location. You can add a file on spawning and delete when getting killed. In the shutdown hook, every process checks how many files are there in the centralised location or how many nodes are there in the zookeeper. If the value is 1, deactivate the cluster, else only disconnect. There could be other approaches, but this is something you could try. On Sat, Apr 3, 2021 at 12:01 PM DonTequila <[email protected]> wrote: > My standalone Java application is executed as process 1 in the Docker > container. At start it activates the cluster which has persistence enabled. > I'm not using the Ignite script bin/ignite.sh. > > "docker stop" sends a SIGTERM to my java application. My application > shutdown hook gets called where I try to deactivate and then disconnect the > Ignite instance. This works well when only disconnecting, but doesn't work > when deactivating the cluster first. Exception says "Failed to execute > deactivate request, node is stopping." Full stacktrace in my original post. > > Docker waits 10 seconds for a graceful stop of the process before it sends > a > SIGKILL. > > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
