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/rc/databases/configuration/clustering.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -38,7 +38,7 @@ Redis server.
38
38
An instance that belongs to a cluster can manage multiple hash
39
39
slots. This division of the key space, known as _sharding_, is achieved by
40
40
hashing the key names, or parts of these (key hash tags), in order to
41
-
obtain the hash slot in which a key should reside. Redis Cloud supports several [hashing policies]().
41
+
obtain the hash slot in which a key should reside. Redis Cloud supports several [hashing policies](#manage-the-hashing-policy).
42
42
43
43
Even when using multiple Redis processes, the use of a Redis
44
44
Enterprise Cloud cluster is nearly transparent to the application that
@@ -114,7 +114,7 @@ These changes include:
114
114
### Redis hashing policy
115
115
116
116
{{< note >}}
117
-
This policy is available for databases created after MONTH DAY, 2025.
117
+
This policy is available for selected accounts and will be rolled out gradually to other accounts in the future.
118
118
{{< /note >}}
119
119
120
120
The Redis hashing policy is identical to the [hashing policy used by Redis Community Edition]({{< relref "/operate/oss_and_stack/reference/cluster-spec#hash-tags" >}}). This policy is recommended for most users and should be selected if any of the following conditions apply:
0 commit comments