Hi Alexandr, Thanks for the response.
It is with native persistence being enabled. Will there be any difference, with and without persistence ? The docker image and the statefulset is created based on the below ignite documentation: https://github.com/apache/ignite/blob/master/docker/apache-ignite/Dockerfile https://apacheignite.readme.io/docs/stateful-deployment#statefulset-deployment The docker image is based on ignite-2.9.0 release and we had put debug statements in onDisconnected method call but we do not see any of those prints in the case of "kubectl delete pod" Also what is the code in ignite which handles KILL SIG ? *Thanks & Regards,* *Vishwas * On Fri, Jan 15, 2021 at 8:10 PM Alexandr Shapkin <lexw...@gmail.com> wrote: > Hi, > > > > Thanks for the ticket. I’ll check that. > > > > What configuration do you use, is it a persistent cluster or in-memory one? > > Do you use an official Ignite image or a custom assembly? > > > > 'kubectl delete pod' should work fine here and forward KILL SIG to a > running node internally. > > Well, at least starting from 2.9 version. > > > > > > *From: *vbm <bmvish...@gmail.com> > *Sent: *Wednesday, January 13, 2021 11:32 AM > *To: *user@ignite.apache.org > *Subject: *Ignite best practice for restarting k8s pod > > > > Hi, > > > > I had raised this ticket: > > https://issues.apache.org/jira/browse/IGNITE-13974 > > > > > > Currently I do not see any cleanup functions getting called when we do a > > 'kubectl delete pod'. > > > > May I know, what is the best practice for restarting k8s ignite pod ? > > How do we handle scenario when we need to scale down Ignite pods ? I think > > internally when we do kubectl scale down it calls kubectl delete pod. > > > > > > Regards, > > Vishwas > > > > > > > > -- > > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ > > >
