You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/operate/rs/7.8/clusters/add-node.md
+10-10Lines changed: 10 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,12 +17,12 @@ After you install the first node, you can add more nodes to the cluster.
17
17
18
18
Before you add a node to the cluster:
19
19
20
-
- The clocks on all nodes must always be [synchronized]({{< relref "/operate/rs/clusters/configure/sync-clocks.md" >}}).
20
+
- The clocks on all nodes must always be [synchronized]({{< relref "/operate/rs/7.8/clusters/configure/sync-clocks.md" >}}).
21
21
22
22
If the clock in the node you are trying to join to the cluster is not synchronized with the nodes already in the cluster,
23
23
the action fails and an error message is shown indicating that you must synchronize the clocks first.
24
24
25
-
- You must [update the DNS records]({{< relref "/operate/rs/networking/cluster-dns" >}})
25
+
- You must [update the DNS records]({{< relref "/operate/rs/7.8/networking/cluster-dns" >}})
26
26
each time a node is added or replaced.
27
27
28
28
- We recommend that you add nodes one after the other rather than in parallel
@@ -32,16 +32,16 @@ Before you add a node to the cluster:
32
32
33
33
To add a node to an existing cluster:
34
34
35
-
1.[Install the Redis Enterprise Software installation package]({{< relref "/operate/rs/installing-upgrading" >}}) on a clean installation
36
-
of a [supported operating system]({{< relref "/operate/rs/installing-upgrading/install/plan-deployment/supported-platforms.md" >}}).
35
+
1.[Install the Redis Enterprise Software installation package]({{< relref "/operate/rs/7.8/installing-upgrading" >}}) on a clean installation
36
+
of a [supported operating system]({{< relref "/operate/rs/7.8/installing-upgrading/install/plan-deployment/supported-platforms.md" >}}).
37
37
38
38
1. To connect to the Cluster Manager UI of the new Redis Enterprise Software installation, go to: <https://URL or IP address:8443>
39
39
40
40
For example, if you installed Redis Enterprise Software on a machine with IP address 10.0.1.34, go to `https://10.0.1.34:8443`.
41
41
42
42
{{< tip >}}
43
43
The management UI uses TLS encryption with a default certificate.
44
-
You can also [replace the TLS certificate]({{< relref "/operate/rs/security/certificates/updating-certificates" >}})
44
+
You can also [replace the TLS certificate]({{< relref "/operate/rs/7.8/security/certificates/updating-certificates" >}})
45
45
with a custom certificate.
46
46
{{< /tip >}}
47
47
@@ -59,15 +59,15 @@ with a custom certificate.
59
59
60
60
1. Configure storage and network settings:
61
61
62
-
1. Enter a path for [*Ephemeral storage*]({{< relref "/operate/rs/installing-upgrading/install/plan-deployment/persistent-ephemeral-storage" >}}), or leave the default path.
62
+
1. Enter a path for [*Ephemeral storage*]({{< relref "/operate/rs/7.8/installing-upgrading/install/plan-deployment/persistent-ephemeral-storage" >}}), or leave the default path.
63
63
64
-
1. Enter a path for [*Persistent storage*]({{< relref "/operate/rs/installing-upgrading/install/plan-deployment/persistent-ephemeral-storage" >}}),
64
+
1. Enter a path for [*Persistent storage*]({{< relref "/operate/rs/7.8/installing-upgrading/install/plan-deployment/persistent-ephemeral-storage" >}}),
65
65
or leave the default path.
66
66
67
-
1. To enable [*Auto Tiering*]({{< relref "/operate/rs/databases/auto-tiering/" >}}),
67
+
1. To enable [*Auto Tiering*]({{< relref "/operate/rs/7.8/databases/auto-tiering/" >}}),
68
68
select **Enable flash storage** and enter the path to the flash storage.
69
69
70
-
1. If the cluster is configured to support [rack-zone awareness]({{< relref "/operate/rs/clusters/configure/rack-zone-awareness.md" >}}), set the **Rack-zone ID** for the new node.
70
+
1. If the cluster is configured to support [rack-zone awareness]({{< relref "/operate/rs/7.8/clusters/configure/rack-zone-awareness.md" >}}), set the **Rack-zone ID** for the new node.
71
71
72
72
1. If your machine has multiple IP addresses, assign a single IPv4 type address for **Node-to-node communication (internal traffic)** and multiple IPv4/IPv6 type addresses for **External traffic**.
73
73
@@ -92,4 +92,4 @@ We recommend that you verify the node is functioning properly using one of the f
92
92
93
93
- Command-line method:
94
94
95
-
Run the [`rlcheck`]({{< relref "/operate/rs/references/cli-utilities/rlcheck" >}}) utility from the node's command line.
95
+
Run the [`rlcheck`]({{< relref "/operate/rs/7.8/references/cli-utilities/rlcheck" >}}) utility from the node's command line.
Copy file name to clipboardExpand all lines: content/operate/rs/7.8/clusters/cluster-recovery.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -26,15 +26,15 @@ Cluster failure can be caused by:
26
26
To recover a cluster and re-create it as it was before the failure,
27
27
you must restore the cluster configuration `ccs-redis.rdb` to the cluster nodes.
28
28
To recover databases in the new cluster, you must restore the databases from persistence files such as backup files, append-only files (AOF), or RDB snapshots.
29
-
These files are stored in the [persistent storage location]({{< relref "/operate/rs/installing-upgrading/install/plan-deployment/persistent-ephemeral-storage" >}}).
29
+
These files are stored in the [persistent storage location]({{< relref "/operate/rs/7.8/installing-upgrading/install/plan-deployment/persistent-ephemeral-storage" >}}).
30
30
31
31
The cluster recovery process includes:
32
32
33
33
1. Install Redis Enterprise Software on the nodes of the new cluster.
34
34
1. Mount the persistent storage with the recovery files from the original cluster to the nodes of the new cluster.
35
35
1. Recover the cluster configuration on the first node in the new cluster.
36
36
1. Join the remaining nodes to the new cluster.
37
-
1.[Recover the databases]({{< relref "/operate/rs/databases/recover.md" >}}).
37
+
1.[Recover the databases]({{< relref "/operate/rs/7.8/databases/recover.md" >}}).
38
38
39
39
## Prerequisites
40
40
@@ -51,7 +51,7 @@ The cluster recovery process includes:
51
51
52
52
1. (Optional) If you want to recover the cluster to the original cluster nodes, uninstall Redis Enterprise Software from the nodes.
53
53
54
-
1.[Install Redis Enterprise Software]({{< relref "/operate/rs/installing-upgrading/install/install-on-linux" >}}) on the new cluster nodes.
54
+
1.[Install Redis Enterprise Software]({{< relref "/operate/rs/7.8/installing-upgrading/install/install-on-linux" >}}) on the new cluster nodes.
55
55
56
56
The new servers must have the same basic hardware and software configuration as the original servers, including:
57
57
@@ -74,7 +74,7 @@ of the configuration and persistence files on each of the nodes.
74
74
75
75
If you use local persistent storage, place all of the recovery files on each of the cluster nodes.
76
76
77
-
1. To recover the original cluster configuration, run [`rladmin cluster recover`]({{< relref "/operate/rs/references/cli-utilities/rladmin/cluster/recover" >}}) on the first node in the new cluster:
77
+
1. To recover the original cluster configuration, run [`rladmin cluster recover`]({{< relref "/operate/rs/7.8/references/cli-utilities/rladmin/cluster/recover" >}}) on the first node in the new cluster:
@@ -89,7 +89,7 @@ of the configuration and persistence files on each of the nodes.
89
89
When the recovery command succeeds,
90
90
this node is configured as the node from the old cluster that has ID 1.
91
91
92
-
1. To join the remaining servers to the new cluster, run [`rladmin cluster join`]({{< relref "/operate/rs/references/cli-utilities/rladmin/cluster/join">}}) from each new node:
92
+
1. To join the remaining servers to the new cluster, run [`rladmin cluster join`]({{< relref "/operate/rs/7.8/references/cli-utilities/rladmin/cluster/join">}}) from each new node:
1. Run [`rladmin status`]({{< relref "/operate/rs/references/cli-utilities/rladmin/status">}}) to verify the recovered nodes are now active and the databases are pending recovery:
104
+
1. Run [`rladmin status`]({{< relref "/operate/rs/7.8/references/cli-utilities/rladmin/status">}}) to verify the recovered nodes are now active and the databases are pending recovery:
105
105
106
106
```sh
107
107
rladmin status
108
108
```
109
109
110
110
{{< note >}}
111
-
Make sure that you update your [DNS records]({{< relref "/operate/rs/networking/cluster-dns">}})
111
+
Make sure that you update your [DNS records]({{< relref "/operate/rs/7.8/networking/cluster-dns">}})
112
112
with the IP addresses of the new nodes.
113
113
{{< /note >}}
114
114
115
-
After the cluster is recovered, you must [recover the databases]({{< relref "/operate/rs/databases/recover.md">}}).
115
+
After the cluster is recovered, you must [recover the databases]({{< relref "/operate/rs/7.8/databases/recover.md">}}).
@@ -44,7 +44,7 @@ You can change the **Time zone** field to ensure the date, time fields, and log
44
44
45
45
The **Alert Settings** tab lets you configure alerts that are relevant to the entire cluster, such as alerts for cluster utilization, nodes, node utilization, security, and database utilization.
46
46
47
-
You can also configure email server settings and [send alerts by email]({{< relref "/operate/rs/monitoring/v1_monitoring#send-alerts-by-email" >}}) to relevant users.
47
+
You can also configure email server settings and [send alerts by email]({{< relref "/operate/rs/7.8/monitoring/v1_monitoring#send-alerts-by-email" >}}) to relevant users.
Copy file name to clipboardExpand all lines: content/operate/rs/7.8/clusters/configure/license-keys.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,7 +20,7 @@ Trial mode allows all features to be enabled during the trial period.
20
20
21
21
Trial mode is limited to 30 days and 4 shards, including master and replica shards. A new Redis Enterprise Software installation starts its 30-day trial period from the day you set up the cluster on the first node.
22
22
23
-
Trial mode requires a trial license. If you do not provide a license when you create a cluster using the Cluster Manager UI or a [bootstrapping REST API request]({{< relref "/operate/rs/references/rest-api/requests/bootstrap#post-bootstrap" >}}), a trial cluster license is generated by default.
23
+
Trial mode requires a trial license. If you do not provide a license when you create a cluster using the Cluster Manager UI or a [bootstrapping REST API request]({{< relref "/operate/rs/7.8/references/rest-api/requests/bootstrap#post-bootstrap" >}}), a trial cluster license is generated by default.
24
24
25
25
## View cluster license key
26
26
@@ -32,9 +32,9 @@ To view the cluster license key, use:
32
32
33
33
1. Select **Change** to view the cluster license key.
34
34
35
-
- REST API - [`GET /v1/license`]({{< relref "/operate/rs/references/rest-api/requests/license#get-license" >}})
35
+
- REST API - [`GET /v1/license`]({{< relref "/operate/rs/7.8/references/rest-api/requests/license#get-license" >}})
36
36
37
-
For a list of returned fields, see the [response section]({{< relref "/operate/rs/references/rest-api/requests/license#get-response" >}}).
37
+
For a list of returned fields, see the [response section]({{< relref "/operate/rs/7.8/references/rest-api/requests/license#get-response" >}}).
38
38
39
39
{{<note>}}
40
40
As of version 7.2, Redis Enterprise enforces shard limits by shard types, RAM or flash, instead of the total number of shards. The flash shards limit only appears in the UI if Auto Tiering is enabled.
@@ -113,7 +113,7 @@ To change the cluster license alert settings, use one of the following methods:
113
113
1. Click **Save**.
114
114
115
115
116
-
-[Update cluster]({{<relref "/operate/rs/references/rest-api/requests/cluster#put-cluster">}}) REST API request:
116
+
-[Update cluster]({{<relref "/operate/rs/7.8/references/rest-api/requests/cluster#put-cluster">}}) REST API request:
117
117
118
118
The following example changes the cluster license alert to occur 30 days before the cluster license expiration date:
0 commit comments