Skip to content

Commit 9eceea5

Browse files
authored
Apply suggestions from code review
1 parent 9faeeb3 commit 9eceea5

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

content/operate/rc/databases/configuration/clustering.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -38,7 +38,7 @@ Redis server.
3838
An instance that belongs to a cluster can manage multiple hash
3939
slots. This division of the key space, known as _sharding_, is achieved by
4040
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).
4242

4343
Even when using multiple Redis processes, the use of a Redis
4444
Enterprise Cloud cluster is nearly transparent to the application that
@@ -114,7 +114,7 @@ These changes include:
114114
### Redis hashing policy
115115

116116
{{< 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.
118118
{{< /note >}}
119119

120120
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

Comments
 (0)