From c0bebbc9554965bc9482c784360e550632cbf507 Mon Sep 17 00:00:00 2001 From: reeb Date: Wed, 20 May 2026 02:35:12 +0300 Subject: [PATCH] RDoc-3855 - fix the clustering overview section that explains the license cores caps - per cluster and per node. --- docs/server/clustering/overview.mdx | 18 +++++++++++------- .../version-6.2/server/clustering/overview.mdx | 18 +++++++++++------- .../version-7.0/server/clustering/overview.mdx | 18 +++++++++++------- .../version-7.1/server/clustering/overview.mdx | 18 +++++++++++------- 4 files changed, 44 insertions(+), 28 deletions(-) diff --git a/docs/server/clustering/overview.mdx b/docs/server/clustering/overview.mdx index 4a8e0b945a..bfe410737a 100644 --- a/docs/server/clustering/overview.mdx +++ b/docs/server/clustering/overview.mdx @@ -67,12 +67,16 @@ across a fault-tolerant, [High-Availability](https://en.wikipedia.org/wiki/High- * A cluster is limited in the maximum number of CPU cores that can be used by all of its nodes at a given time. -* This limit is determined by the cluster's RavenDB license. For example, a Community licensed -cluster can have up to 3 cores. This means that when there is just one node in the cluster, it -can use 1-3 cores. If there are 3 nodes, each will use 1 core (since a server is allowed to be -assigned with at least 1 core). -* The number of assigned cores is divided evenly between all the nodes of a cluster. -* The maximum number of cores a node can use can be limited - [using Studio](../../studio/cluster/cluster-view.mdx#reassign-cores). +* This limit is determined by the cluster's RavenDB license, which can cap both the total +cores used by the cluster and the cores used by any single node. +For example, a Community license allows up to 3 cores in the cluster, with no more than +2 cores on any single node: + * A single-node Community cluster can use up to 2 cores. + * In a 3-node Community cluster each node can use only 1 core, since the cluster cap + is 3 and every node must be assigned at least 1 core. +* By default each node uses all of its hardware cores, up to the per-node cap. To +lower a node's count (for example, to bring the cluster total within the cluster +cap), use [Reassign Cores](../../studio/cluster/cluster-view.mdx#reassign-cores) +in Studio. diff --git a/versioned_docs/version-6.2/server/clustering/overview.mdx b/versioned_docs/version-6.2/server/clustering/overview.mdx index 75a998a815..d97533ceff 100644 --- a/versioned_docs/version-6.2/server/clustering/overview.mdx +++ b/versioned_docs/version-6.2/server/clustering/overview.mdx @@ -66,12 +66,16 @@ across a fault-tolerant, [High-Availability](https://en.wikipedia.org/wiki/High- * A cluster is limited in the maximum number of CPU cores that can be used by all of its nodes at a given time. -* This limit is determined by the cluster's RavenDB license. For example, a Community licensed -cluster can have up to 3 cores. This means that when there is just one node in the cluster, it -can use 1-3 cores. If there are 3 nodes, each will use 1 core (since a server is allowed to be -assigned with at least 1 core). -* The number of assigned cores is divided evenly between all the nodes of a cluster. -* The maximum number of cores a node can use can be limited - [using Studio](../../studio/cluster/cluster-view.mdx#reassign-cores). +* This limit is determined by the cluster's RavenDB license, which can cap both the total +cores used by the cluster and the cores used by any single node. +For example, a Community license allows up to 3 cores in the cluster, with no more than +2 cores on any single node: + * A single-node Community cluster can use up to 2 cores. + * In a 3-node Community cluster each node can use only 1 core, since the cluster cap + is 3 and every node must be assigned at least 1 core. +* By default each node uses all of its hardware cores, up to the per-node cap. To +lower a node's count (for example, to bring the cluster total within the cluster +cap), use [Reassign Cores](../../studio/cluster/cluster-view.mdx#reassign-cores) +in Studio. diff --git a/versioned_docs/version-7.0/server/clustering/overview.mdx b/versioned_docs/version-7.0/server/clustering/overview.mdx index 75a998a815..d97533ceff 100644 --- a/versioned_docs/version-7.0/server/clustering/overview.mdx +++ b/versioned_docs/version-7.0/server/clustering/overview.mdx @@ -66,12 +66,16 @@ across a fault-tolerant, [High-Availability](https://en.wikipedia.org/wiki/High- * A cluster is limited in the maximum number of CPU cores that can be used by all of its nodes at a given time. -* This limit is determined by the cluster's RavenDB license. For example, a Community licensed -cluster can have up to 3 cores. This means that when there is just one node in the cluster, it -can use 1-3 cores. If there are 3 nodes, each will use 1 core (since a server is allowed to be -assigned with at least 1 core). -* The number of assigned cores is divided evenly between all the nodes of a cluster. -* The maximum number of cores a node can use can be limited - [using Studio](../../studio/cluster/cluster-view.mdx#reassign-cores). +* This limit is determined by the cluster's RavenDB license, which can cap both the total +cores used by the cluster and the cores used by any single node. +For example, a Community license allows up to 3 cores in the cluster, with no more than +2 cores on any single node: + * A single-node Community cluster can use up to 2 cores. + * In a 3-node Community cluster each node can use only 1 core, since the cluster cap + is 3 and every node must be assigned at least 1 core. +* By default each node uses all of its hardware cores, up to the per-node cap. To +lower a node's count (for example, to bring the cluster total within the cluster +cap), use [Reassign Cores](../../studio/cluster/cluster-view.mdx#reassign-cores) +in Studio. diff --git a/versioned_docs/version-7.1/server/clustering/overview.mdx b/versioned_docs/version-7.1/server/clustering/overview.mdx index 75a998a815..d97533ceff 100644 --- a/versioned_docs/version-7.1/server/clustering/overview.mdx +++ b/versioned_docs/version-7.1/server/clustering/overview.mdx @@ -66,12 +66,16 @@ across a fault-tolerant, [High-Availability](https://en.wikipedia.org/wiki/High- * A cluster is limited in the maximum number of CPU cores that can be used by all of its nodes at a given time. -* This limit is determined by the cluster's RavenDB license. For example, a Community licensed -cluster can have up to 3 cores. This means that when there is just one node in the cluster, it -can use 1-3 cores. If there are 3 nodes, each will use 1 core (since a server is allowed to be -assigned with at least 1 core). -* The number of assigned cores is divided evenly between all the nodes of a cluster. -* The maximum number of cores a node can use can be limited - [using Studio](../../studio/cluster/cluster-view.mdx#reassign-cores). +* This limit is determined by the cluster's RavenDB license, which can cap both the total +cores used by the cluster and the cores used by any single node. +For example, a Community license allows up to 3 cores in the cluster, with no more than +2 cores on any single node: + * A single-node Community cluster can use up to 2 cores. + * In a 3-node Community cluster each node can use only 1 core, since the cluster cap + is 3 and every node must be assigned at least 1 core. +* By default each node uses all of its hardware cores, up to the per-node cap. To +lower a node's count (for example, to bring the cluster total within the cluster +cap), use [Reassign Cores](../../studio/cluster/cluster-view.mdx#reassign-cores) +in Studio.