[JAMES-3108] James should shutdown gracefully

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 3.5.0
• Assignee: Unassigned
• Reporter: Benoit Tellier
• Created: 08/Mar/20 15:10
• Updated: 09/Mar/20 10:49
• Resolved: 09/Mar/20 10:49

Description

James should not shut down immediatly on SIGTERM, but it gracefully terminates connections.

In a kubernetes context for instance:

It might take some time before a component such as kube-proxy or the Ingress controller is notified of the endpoint changes.

Hence, traffic might still flow to the Pod despite it being marked as terminated.

The app should stop accepting new requests on all remaining connections, and close these once the outgoing queue is drained.

If you need a refresher on how endpoints are propagated in your cluster, read this article on how to handle client requests properly.

(Source: https://learnk8s.io/production-best-practices)

I think it also makes sens out of this context.

A graceful shutdown furthermore decrease the risk of inconsistencies in the underlying datastores (Cassandra)