The thread dump is key - typically what I have found is there are user threads. The Java Virtual Machine will not exit if there are any user threads. So make sure any plugins have Thread.setDeamon(true) when the plugin launches a background thread.
If that plugin is a third party - may be open a ticket with that third-party library. Charlie On Wed, Aug 14, 2019 at 6:41 AM Jens Deppe <jde...@pivotal.io> wrote: > It's always preferable to use SIGTERM as that signal is able to be trapped > and will attempt to shut down the process gracefully. SIGKILL is not > trappable (and cannot be blocked by the process) and will cause a hard > shutdown of the process. SIGABRT is essentially the same as SIGKILL and > will not perform a clean shutdown. > > --Jens > > On Wed, Aug 14, 2019 at 6:26 AM Jacob Barrett <jbarr...@pivotal.io> wrote: > >> If it doesn't come down gracefully then take a thread dump and report the >> issue here. After that it really doesn’t matter how you terminate it, it’s >> ending in an undefined state either way. >> >> -Jake >> >> >> On Aug 14, 2019, at 2:50 AM, aashish choudhary < >> aashish.choudha...@gmail.com> wrote: >> >> Any thoughts on this? >> On Wed, Aug 14, 2019, 1:13 AM aashish choudhary < >> aashish.choudha...@gmail.com> wrote: >> >>> What is the recommended way to kill geode process. We use shutdown and >>> stop commands to stop server/servers but sometimes it doesn't work and we >>> end up using kill -9. Which I don't think is the right way to kill as we >>> have persistence enabled and it terminates the process abruptly. >>> >>> Then option left is SIGABRT VS SIGTERM? >>> >>> >>> With best regards, >>> Ashish >>> >> -- Charlie Black | cbl...@pivotal.io
