<p>I deployed gridgain cluster in google kubernetes cluster following[1]. I enabled native persistency using statefulset. In statefulset.yaml in [2] <strong>terminationGracePeriodSeconds</strong> set to <strong>60000</strong>. What is the purpose of this large timeout?</p>
<p>When deleting pod using <strong>kubectl delete pod</strong> command it take very large time. What is the suitable value for <strong>terminationGracePeriodSeconds</strong> without loss any data.</p>
<p>[1]. <a href="https://www.gridgain.com/docs/latest/installation-guide/kubernetes/gke-deployment" rel="nofollow noreferrer">https://www.gridgain.com/docs/latest/installation-guide/kubernetes/gke-deployment</a></p>
<p>[2]. <a href="https://www.gridgain.com/docs/latest/installation-guide/kubernetes/gke-deployment#creating-pod-configuration" rel="nofollow noreferrer">https://www.gridgain.com/docs/latest/installation-guide/kubernetes/gke-deployment#creating-pod-configuration</a></p>

Nuwan Sameera
<p>I believe the reason behind setting it to 60000 was - do not rely on it. Prior to Ignite 2.9 there was an issue with the startup script that didn't bypass SYS SIGNAL to the underlying Java app, making it impossible to perform a graceful shutdown.</p>
<p>If a node is being restarted gracefully and <a href="https://www.gridgain.com/docs/latest/developers-guide/starting-nodes#preventing-partition-loss-on-shutdown" rel="nofollow noreferrer">IGNITE_WAIT_FOR_BACKUPS_ON_SHUTDOWN</a> is enabled, Ignite will ensure that the node leave won't lead to a data loss. Sometimes a rebalance might take a while.</p>
<p>Keeping the above in mind: the hang issue might happen for Apache Ignite 2.8 and below, keeping the recommended terminationGracePeriodSeconds should be fine and never be used in practice (in a normal flow).</p>
