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 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/ |
- Ignite best practice for restarting k8s pod vbm
- RE: Ignite best practice for restarting k8s pod Alexandr Shapkin
- Re: Ignite best practice for restarting k8s pod Vishwas Bm
- Re: Ignite best practice for restarting k8s ... Raymond Wilson
