Skip to content

Commit 953606a

Browse files
as51340matea16
andauthored
docs: HA system configuration (#1416)
* docs: Extract HA system configuration * Update pages/getting-started/install-memgraph/kubernetes.mdx --------- Co-authored-by: Matea Pesic <[email protected]>
1 parent 918775e commit 953606a

File tree

2 files changed

+13
-10
lines changed

2 files changed

+13
-10
lines changed

pages/clustering/high-availability.mdx

Lines changed: 10 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -59,15 +59,6 @@ metrics which reveal us p50, p90 and p99 latencies of RPC messages, the duration
5959
in the cluster. We are also counting the number of different RPC messages exchanged and the number of failed requests since this can give
6060
us information about parts of the cluster that need further care. You can see the full list of metrics [here](/database-management/monitoring#system-metrics).
6161

62-
<Callout type="info">
63-
64-
When deploying coordinators to servers, you can use the instance of almost any size. Instances of 4GiB or 8GiB will suffice since coordinators'
65-
job mainly involves network communication and storing Raft metadata. Coordinators and data instances can be deployed on same servers (pairwise)
66-
but from the availability perspective, it is better to separate them physically.
67-
68-
</Callout>
69-
70-
7162
## Bolt+routing
7263

7364
Directly connecting to the main instance isn't preferred in the HA cluster since
@@ -127,6 +118,16 @@ queries, not coordinator-based queries.
127118

128119
## System configuration
129120

121+
122+
When deploying coordinators to servers, you can use the instance of almost any size. Instances of 4GiB or 8GiB will suffice since coordinators'
123+
job mainly involves network communication and storing Raft metadata. Coordinators and data instances can be deployed on same servers (pairwise)
124+
but from the availability perspective, it is better to separate them physically.
125+
126+
When setting up disk space, you should always make sure that there is at least space for `--snapshot-retention-count+1` snapshots + few WAL files. That's
127+
because we first create (N+1)th snapshot and then delete the oldest one so we could guarantee that the creation of a new snapshot ended successfully. This is
128+
especially important when using Memgraph HA in K8s, since in K8s there is usually a limit set on the disk space used.
129+
130+
130131
<Callout type="warning">
131132
Important note if you're using native Memgraph deployment with Red Hat.
132133

pages/getting-started/install-memgraph/kubernetes.mdx

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -329,14 +329,16 @@ reference guide](/database-management/configuration).
329329
330330
A Helm chart for deploying Memgraph in [high availability (HA)
331331
setup](/clustering/high-availability). This helm chart requires [Memgraph
332-
Enterprise license](/database-management/enabling-memgraph-enterprise).
332+
Enterprise license](/database-management/enabling-memgraph-enterprise). We recommend reading
333+
the documentation about [high availability](https://memgraph.com/docs/clustering/high-availability) in Memgraph.
333334
334335
Memgraph HA cluster includes 3 coordinators and 2 data instances by default. Since
335336
multiple Memgraph instances are used, it is advised to use multiple workers nodes in Kubernetes.
336337
Our advice is that each Memgraph instance gets on its own node. The size of nodes on which
337338
data pods will reside depends on the computing power and the memory you need to store data.
338339
Coordinator nodes can be smaller and machines with basic requirements met (8-16 GB of RAM) will be enough.
339340
341+
340342
### Installing the Memgraph HA Helm chart
341343
342344
To include Memgraph HA cluster as a part of your Kubernetes cluster, you need to

0 commit comments

Comments
 (0)