Memgraph 2.18 documentation

pages/clustering/high-availability.mdx

@@ -304,8 +304,8 @@ the flag to more than `--instance-down-timeout-sec`, as it is needed first to co
 ### Determining instance's health
 
 Every `--instance-health-check-frequency-sec` seconds, the coordinator contacts each instance. 
-The instance is not considered to be down unless `--instance-down-timeout-sec` has passed and the instance hasn't responded to the coordinator in the meantime. Expectation currently is to set `--instance-health-check-frequency-sec`
-to be less than `--instance-down-timeout-sec` and for `--instance-down-timeout-sec` to be multiplier of `--instance-health-check-frequency-sec` with coefficient N.
+The instance is not considered to be down unless `--instance-down-timeout-sec` has passed and the instance hasn't responded to the coordinator in the meantime. Users must set `--instance-health-check-frequency-sec`
+to be less or equal to the `--instance-down-timeout-sec` but we advise users to set `--instance-down-timeout-sec` to a multiplier of `--instance-health-check-frequency-sec`.
 Set the multiplier coefficient to be N>=2. For example, set `--instance-down-timeout-sec=5` and `--instance-health-check-frequency-sec=1` which will result in coordinator
 contacting each instance every 1 second and the instance is considered dead after it doesn't respond 5 times (5 seconds / 1 second).
 
@@ -547,12 +547,12 @@ docker run  --name coord1 -p 7690:7690 -p 7444:7444 memgraph/memgraph-mage --bol
 
 2. Start coordinator2:
 ```plaintext
-docker run  --name coord2 -p 7691:7691 -p 7445:7444 memgraph/memgraph-mage --bolt-port=7691 --log-level=TRACE --data-directory=/tmp/mg_data_coord2 --log-file=/tmp/coord2.log --also-log-to-stderr --coordinator-id=2 --coordinator-port=10112 --experimental-enabled=high-availability
+docker run  --name coord2 -p 7691:7691 -p 7445:7444 memgraph/memgraph-mage --bolt-port=7691 --log-level=TRACE --data-directory=/tmp/mg_data_coord2 --log-file=/tmp/coord2.log --nuraft-log-file=/tmp/nuraft/coord2.log --also-log-to-stderr --coordinator-id=2 --coordinator-port=10112 --experimental-enabled=high-availability
 ```
 
 3. Start coordinator3:
 ```plaintext
-docker run  --name coord3 -p 7692:7692 -p 7446:7444 memgraph/memgraph-mage --bolt-port=7692 --log-level=TRACE --data-directory=/tmp/mg_data_coord3 --log-file=/tmp/coord3.log --also-log-to-stderr --coordinator-id=3 --coordinator-port=10113 --experimental-enabled=high-availability
+docker run  --name coord3 -p 7692:7692 -p 7446:7444 memgraph/memgraph-mage --bolt-port=7692 --log-level=TRACE --data-directory=/tmp/mg_data_coord3 --log-file=/tmp/coord3.log --nuraft-log-file=/tmp/nuraft/coord1.log --also-log-to-stderr --coordinator-id=3 --coordinator-port=10113 --experimental-enabled=high-availability
 ```
 
 4. Start instance1:

pages/database-management/configuration.mdx

@@ -407,14 +407,17 @@ This section contains the list of flags that are used to configure [experimental
 
 This section contains the list of flags that are used to configure highly available cluster in Memgraph.
 
-| Flag                                     | Description                                                                                                 | Type       |
-|------------------------------------------|-------------------------------------------------------------------------------------------------------------|------------|
-| --raft-server-id                         | Raft server id on coordinator instance.                                                                     | `[uint32]` |
-| --raft-server-port                       | Raft server's port on coordinator instance.                                                                 | `[uint32]` |
-| --coordinator-server-port                | Port on which replication instances receive messages from the coordinator.                                  | `[uint32]` |
-| --instance-health-check-frequency-sec=1  | The interval between two health checks that the coordinator does on replication instances.                  | `[uint32]` |
-| --instance-down-timeout-sec=5            | Number of seconds that need to pass before replication instance is considered down.                         | `[uint32]` |
-| --instance-get-uuid-frequency-sec=10     | The interval between two instance uuid checks.                                                              | `[uint32]` |
+
+| Flag                                     | Description                                                                                                                                                  | Type       |
+|------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|
+| --raft-server-id                         | Raft server id on coordinator instance.                                                                                                                      | `[uint32]` |
+| --raft-server-port                       | Raft server's port on coordinator instance.                                                                                                                  | `[uint32]` |
+| --coordinator-server-port                | Port on which replication instances receive messages from coordinator .                                                                                      | `[uint32]` |
+| --instance-health-check-frequency-sec=1  | The interval between two health checks that coordinator does on replication instances.                                                                       | `[uint32]` |
+| --instance-down-timeout-sec=5            | Number of seconds that need to pass before replication instance is considered down. Must be greater or equal to the `--instance-health-check-frequency-sec`. | `[uint32]` |
+| --instance-get-uuid-frequency-sec=10     | The interval between two instance uuid checks.                                                                                                               | `[uint32]` |
+| --nuraft-log-file                        | Path to the file where NuRaft logs are saved.                                                                                                                | `[string]` |
+
 
 ### Query