This is an automated email from the ASF dual-hosted git repository.
sk0x50 pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/ignite-3.git
The following commit(s) were added to refs/heads/main by this push:
new abc53da67c0 IGNITE-28214 Cluster name can be changed (#7771)
abc53da67c0 is described below
commit abc53da67c081e343c4ae78d9ba76bde9e78c2b2
Author: jinxxxoid <[email protected]>
AuthorDate: Fri Apr 3 16:36:40 2026 +0400
IGNITE-28214 Cluster name can be changed (#7771)
---
docs/docs/configure-and-operate/operations/lifecycle.md | 2 +-
docs/docs/configure-and-operate/reference/cluster-configuration.md | 4 ++++
docs/docs/tools/cli-commands.md | 2 +-
3 files changed, 6 insertions(+), 2 deletions(-)
diff --git a/docs/docs/configure-and-operate/operations/lifecycle.md
b/docs/docs/configure-and-operate/operations/lifecycle.md
index c1c56288235..3d96756e96f 100644
--- a/docs/docs/configure-and-operate/operations/lifecycle.md
+++ b/docs/docs/configure-and-operate/operations/lifecycle.md
@@ -60,7 +60,7 @@ To restore full cluster functionality, bring the offline
members of CMG back onl
The CMG stores the following information:
-- Current cluster state, including what nodes are in CMG and metastorage
groups, what Ignite version is used and cluster tag.
+- Current cluster state, including what nodes are in CMG and metastorage
groups, what Ignite version is used and cluster tag. The cluster name can be
changed after initialization.
- Consistent IDs of all nodes in the logical topology.
- Node validation status.
diff --git a/docs/docs/configure-and-operate/reference/cluster-configuration.md
b/docs/docs/configure-and-operate/reference/cluster-configuration.md
index 50fc351d3b6..83b6bedbfce 100644
--- a/docs/docs/configure-and-operate/reference/cluster-configuration.md
+++ b/docs/docs/configure-and-operate/reference/cluster-configuration.md
@@ -6,6 +6,10 @@ sidebar_label: Cluster Configuration
Ignite 3 cluster configuration is shared across the whole cluster. Regardless
of which node you apply the configuration on, it will be propagated to all
nodes in the cluster.
+:::note
+The cluster name is not part of the standard cluster configuration and cannot
be changed with `cluster config update`. To rename a cluster after
initialization, use the [REST API](/3.1.0/tools/rest-api#renaming-a-cluster).
+:::
+
In Ignite 3, you can create and maintain configuration in either HOCON or
JSON. The configuration file has a single root "node," called `ignite`. All
configuration sections are children, grandchildren, etc., of that node.
## Checking Cluster Configuration
diff --git a/docs/docs/tools/cli-commands.md b/docs/docs/tools/cli-commands.md
index 0d2ffee4dd0..001752cd019 100644
--- a/docs/docs/tools/cli-commands.md
+++ b/docs/docs/tools/cli-commands.md
@@ -389,7 +389,7 @@ cluster init --name=<clusterName>
[--metastorage-group=<nodeNames>] [--cluster-m
| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
-| `--name` | Option | Yes | Human-readable name of the cluster. |
+| `--name` | Option | Yes | Human-readable name of the cluster. Can be changed
after initialization. |
| `--metastorage-group` | Option | No | Metastorage group nodes
(comma-separated list). |
| `--cluster-management-group` | Option | No | Names of nodes that will host
the Cluster Management Group (comma-separated list). |
| `--config` | Option | No | Cluster configuration that will be applied during
initialization. |
