summaryrefslogtreecommitdiffstats
path: root/iredis/data/commands/cluster-saveconfig.md
diff options
context:
space:
mode:
authorDaniel Baumann <daniel.baumann@progress-linux.org>2020-03-21 10:28:17 +0000
committerDaniel Baumann <daniel.baumann@progress-linux.org>2021-02-07 11:16:53 +0000
commit06cba6ccd165ca8b224797e37fccb9e63f026d77 (patch)
treee82f1bc439997ae296f2e74f8a64d84c5d95f140 /iredis/data/commands/cluster-saveconfig.md
parentInitial commit. (diff)
downloadiredis-06cba6ccd165ca8b224797e37fccb9e63f026d77.tar.xz
iredis-06cba6ccd165ca8b224797e37fccb9e63f026d77.zip
Adding upstream version 1.9.1.upstream/1.9.1
Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>
Diffstat (limited to 'iredis/data/commands/cluster-saveconfig.md')
-rw-r--r--iredis/data/commands/cluster-saveconfig.md15
1 files changed, 15 insertions, 0 deletions
diff --git a/iredis/data/commands/cluster-saveconfig.md b/iredis/data/commands/cluster-saveconfig.md
new file mode 100644
index 0000000..115d88a
--- /dev/null
+++ b/iredis/data/commands/cluster-saveconfig.md
@@ -0,0 +1,15 @@
+Forces a node to save the `nodes.conf` configuration on disk. Before to return
+the command calls `fsync(2)` in order to make sure the configuration is flushed
+on the computer disk.
+
+This command is mainly used in the event a `nodes.conf` node state file gets
+lost / deleted for some reason, and we want to generate it again from scratch.
+It can also be useful in case of mundane alterations of a node cluster
+configuration via the `CLUSTER` command in order to ensure the new configuration
+is persisted on disk, however all the commands should normally be able to auto
+schedule to persist the configuration on disk when it is important to do so for
+the correctness of the system in the event of a restart.
+
+@return
+
+@simple-string-reply: `OK` or an error if the operation fails.