summaryrefslogtreecommitdiffstats
path: root/iredis/data/commands/cluster-saveconfig.md
diff options
context:
space:
mode:
Diffstat (limited to 'iredis/data/commands/cluster-saveconfig.md')
-rw-r--r--iredis/data/commands/cluster-saveconfig.md16
1 files changed, 8 insertions, 8 deletions
diff --git a/iredis/data/commands/cluster-saveconfig.md b/iredis/data/commands/cluster-saveconfig.md
index 115d88a..31308c2 100644
--- a/iredis/data/commands/cluster-saveconfig.md
+++ b/iredis/data/commands/cluster-saveconfig.md
@@ -1,14 +1,14 @@
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.
+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
+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.
+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