From fe8f80bdd8c6bdcfaf4aea7ccb5957b9adf90cc9 Mon Sep 17 00:00:00 2001
From: Michael Hanselmann <hansmi@google.com>
Date: Wed, 14 Nov 2012 09:02:53 +0100
Subject: [PATCH] Document master daemon's shutdown behaviour

This wasn't clearly documented until now.

Signed-off-by: Michael Hanselmann <hansmi@google.com>
Reviewed-by: Iustin Pop <iustin@google.com>
---
 man/ganeti-masterd.rst | 12 ++++++++++++
 1 file changed, 12 insertions(+)

diff --git a/man/ganeti-masterd.rst b/man/ganeti-masterd.rst
index 51592779d..2502d65d6 100644
--- a/man/ganeti-masterd.rst
+++ b/man/ganeti-masterd.rst
@@ -55,6 +55,18 @@ skip this process. The option requires interactive confirmation, as
 having two masters on the same cluster is a very dangerous
 situation and will most likely lead to data loss.
 
+SHUTDOWN
+~~~~~~~~
+
+When the master daemon receives a ``SIGINT`` (Ctrl-C) or ``SIGTERM``
+signal, it stops accepting new jobs and prepares to shut down shortly
+after jobs running at the time finish. Meanwhile it still responds to
+LUXI requests. Pending jobs are re-queued after the daemon is started
+again. When a second signal is received, the master daemon terminates
+without waiting (it might still need to wait for some threads to
+finish). Note that the latter, as well as sending ``SIGKILL``, may leave
+the cluster in an inconsistent state.
+
 JOB QUEUE
 ~~~~~~~~~
 
-- 
GitLab