[Feature] Graceful shutdown

Description

I'm using graph-node in kubernetes with a sql proxy to connect to postgresql.

When I do a replace of the graph-node, kubernetes sends a SIGTERM and will wait 30s before forcing a shutdown.
I'm waiting 30s in the SQL proxy to let the graph-node to finish its queries.
But the graph-node does not stop, It just sends errors because the database goes away and waits for kubernetes to force the kill of the pod.

A nice feature would be to permit a graceful shutdown of the graph-node.
It should stop indexing on SIGTERM, finish its sql queries and disconnect to the database.
More, it can prevent some unexpected issues in postgresql database like bad block caching.

An indexer node or query has actually the same behaviour.

Are you aware of any blockers that must be resolved before implementing this feature? If so, which? Link to any relevant GitHub issues.

No response

Some information to help us out

• Tick this box if you plan on implementing this feature yourself.
• I have searched the issue tracker to make sure this issue is not a duplicate.

Commencez par retracer la manière dont graph-node gère SIGTERM et dont ses processus d’indexation et de requête sont arrêtés. Vérifiez le comportement à l’arrêt avec Kubernetes et le SQL proxy, puis vérifiez que l’indexation s’arrête, que les requêtes SQL en cours se terminent et que la connexion PostgreSQL est déconnectée avant la fin de la fenêtre de terminaison de 30 secondes.