From 85e67dfce6c56664a4c69de2a1c32ae0871a5d78 Mon Sep 17 00:00:00 2001 From: Sebastian Bernauer Date: Thu, 2 Nov 2023 08:47:00 +0100 Subject: [PATCH] Update docs/modules/hdfs/pages/usage-guide/operations/graceful-shutdown.adoc Co-authored-by: Siegfried Weber --- .../hdfs/pages/usage-guide/operations/graceful-shutdown.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/modules/hdfs/pages/usage-guide/operations/graceful-shutdown.adoc b/docs/modules/hdfs/pages/usage-guide/operations/graceful-shutdown.adoc index 7893554c..c5ba0d1c 100644 --- a/docs/modules/hdfs/pages/usage-guide/operations/graceful-shutdown.adoc +++ b/docs/modules/hdfs/pages/usage-guide/operations/graceful-shutdown.adoc @@ -7,7 +7,7 @@ You can configure the graceful shutdown as described in xref:concepts:operations As a default, JournalNodes have `15 minutes` to shut down gracefully. The JournalNode process will always run as PID `1` and will receive a `SIGTERM` signal when Kubernetes wants to terminate the Pod. -It will log the received signal as show in the log below and initiate a graceful shutdown. +It will log the received signal as shown in the log below and initiate a graceful shutdown. After the graceful shutdown timeout runs out, and the process still didn't exit, Kubernetes will issue a `SIGKILL` signal. https://github.com/apache/hadoop/blob/a585a73c3e02ac62350c136643a5e7f6095a3dbb/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/qjournal/server/JournalNode.java#L272[This] is the relevant code that gets executed in the JournalNodes as of HDFS version `3.3.4`.