diff options
| author | Daniel Baumann <daniel.baumann@progress-linux.org> | 2023-01-04 07:19:32 +0000 |
|---|---|---|
| committer | Daniel Baumann <daniel.baumann@progress-linux.org> | 2023-01-04 07:19:32 +0000 |
| commit | 7480e618ec785ba8a1c74c8a150cffe5880fb3bb (patch) | |
| tree | 87422376dd9a7eee55850f0fce9a8bb4c13e44a2 /iredis/data/commands/cluster-saveconfig.md | |
| parent | Adding upstream version 1.12.1. (diff) | |
| download | iredis-upstream/1.13.0.tar.xz iredis-upstream/1.13.0.zip | |
Adding upstream version 1.13.0.upstream/1.13.0
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.md | 16 |
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 |