Skip to content

Commit caa2cbf

Browse files
committed
Merge branch 'main' into release-rs-gilboa
2 parents 3fff409 + fca85d4 commit caa2cbf

File tree

11 files changed

+150
-21
lines changed

11 files changed

+150
-21
lines changed

content/commands/acl-list.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -44,6 +44,10 @@ configuration file if you wish (but make sure to check [`ACL SAVE`]({{< relref "
4444
2) "user default on nopass ~* &* +@all"
4545
```
4646

47+
{{< note >}}
48+
In some cases, you might see `allchannels` instead of `&*` and `allkeys` instead of `~*` in the output. This is because `allchannels` and `allkeys` are aliases for `&*` and `~*` respectively.
49+
{{< /note>}}
50+
4751
## Return information
4852

4953
{{< multitabs id="acl-list-return-info"

content/develop/ai/search-and-query/administration/configuration.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ title: Configuration parameters
1818
weight: 1
1919
---
2020
{{< note >}}
21-
As of Redis 8 in Redis Open Source (Redis 8), configuration parameters for the time series data structure are now set in the following ways:
21+
As of Redis 8 in Redis Open Source (Redis 8), configuration parameters for Redis Query Engine (RQE) are now set in the following ways:
2222
* At load time via your `redis.conf` file.
2323
* At run time (where applicable) using the [`CONFIG SET`]({{< relref "/commands/config-set" >}}) command.
2424

content/develop/clients/jedis/_index.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,7 @@ To include `Jedis` as a dependency in your application, edit the dependency file
3434
<dependency>
3535
<groupId>redis.clients</groupId>
3636
<artifactId>jedis</artifactId>
37-
<version>6.0.0</version>
37+
<version>6.1.0</version>
3838
</dependency>
3939
```
4040

@@ -46,7 +46,7 @@ To include `Jedis` as a dependency in your application, edit the dependency file
4646
}
4747
//...
4848
dependencies {
49-
implementation 'redis.clients:jedis:6.0.0'
49+
implementation 'redis.clients:jedis:6.1.0'
5050
//...
5151
}
5252
```

content/operate/kubernetes/logs/_index.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -42,6 +42,6 @@ sideContainersSpec:
4242
4343
Now the logs can be accessed from in the sidecar. For example by running
4444
45-
```kubectl exec -it <pod-name> -c busybox tail home/logs/supervisord.log```
45+
```kubectl exec -it <pod-name> -c busybox -- tail home/logs/supervisord.log```
4646

4747
The sidecar container is user determined and can be used to format, process and share logs in a specified format and protocol.

content/operate/kubernetes/reference/api/redis_enterprise_database_api.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -5,6 +5,7 @@ categories:
55
- docs
66
- operate
77
- kubernetes
8+
aliases: /operate/kubernetes/reference/redis_enterprise_cluster_api
89
linkTitle: REDB API
910
weight: 30
1011
---

content/operate/kubernetes/release-notes/7-22-0-releases/7-22-0-17-september2025.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ weight: 0
1313

1414
## Highlights
1515

16-
This is a maintenance release to support [Redis Enterprise Software version 7.22.0-250]({{< relref "/operate/rs/release-notes/rs-7-22-releases/" >}}). For version changes, supported distributions, and known limitations, see the [release notes for 7.22.0-15 (July 2025)]({{< relref "/operate/kubernetes/release-notes/7-22-0-releases/7-22-0-15-july2025" >}}).
16+
This is a maintenance release to support [Redis Enterprise Software version 7.22.0-250]({{< relref "/operate/rs/release-notes/rs-7-22-releases/rs-7-22-0-250" >}}). For version changes, supported distributions, and known limitations, see the [release notes for 7.22.0-15 (July 2025)]({{< relref "/operate/kubernetes/release-notes/7-22-0-releases/7-22-0-15-july2025" >}}).
1717

1818
## Downloads
1919

content/operate/kubernetes/security/configuration-secrets.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -92,4 +92,4 @@ kubectl create secret generic <secret-name> \
9292
- [Manage REC credentials]({{< relref "/operate/kubernetes/security/manage-rec-credentials" >}})
9393
- [Manage REC certificates]({{< relref "/operate/kubernetes/security/manage-rec-certificates" >}})
9494
- [Add client certificates]({{< relref "/operate/kubernetes/security/add-client-certificates" >}})
95-
- [Redis Enterprise Cluster API reference]({{< relref "/operate/kubernetes/reference/redis_enterprise_cluster_api" >}})
95+
- [Redis Enterprise Cluster API reference]({{< relref "/operate/kubernetes/reference/api/redis_enterprise_cluster_api" >}})

content/operate/kubernetes/security/manage-rec-credentials.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -45,7 +45,7 @@ The credentials can be used to access the Redis Enterprise admin console or the
4545
1. Access a [pod](https://kubernetes.io/docs/concepts/workloads/pods/) running a Redis Enterprise cluster.
4646

4747
```sh
48-
kubectl exec -it <rec-resource-name>-0 bash
48+
kubectl exec -it <rec-resource-name>-0 -c redis-enterprise-node -- /bin/bash
4949
```
5050

5151
2. Add a new password for the existing user.
@@ -79,7 +79,7 @@ kubectl apply -f -
7979
5. Access a pod running a Redis Enterprise cluster again.
8080

8181
```sh
82-
kubectl exec -it <rec-resource-name>-0 bash
82+
kubectl exec -it <rec-resource-name>-0 -c redis-enterprise-node -- /bin/bash
8383
```
8484

8585
6. Remove the previous password to ensure only the new one applies.

content/operate/rc/databases/create-database/create-active-active-database.md

Lines changed: 130 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -139,15 +139,137 @@ By default, you're shown basic settings, which include:
139139
- **Throughput**: When you create an Active-Active database, you define the throughput for each instance. The total operations per second combines the total read ops/sec and applies the write ops/sec for each region across every region.
140140

141141
{{<image filename="images/rc/active-active-throughput-detail.png" width="75%" alt="When you create an Active-Active database, you define throughput for each region." >}}
142+
143+
The total ops/sec for each region is calculated as follows:
144+
145+
```sh
146+
Region ops/sec = Local read ops/sec +
147+
Sum of write ops/sec from all regions
148+
```
149+
150+
The total ops/sec for the database is the sum of the ops/sec for each region.
142151

143-
Because each instance needs the ability to write to every other instance, write operations significantly affect the total, as shown in the following table:
144-
145-
| Number of regions | Read operations | Write operations | Total operations |
146-
|:-----------------:|:---------------:|:----------------:|:----------------:|
147-
| Two | 1,000 each | 1,000 each | 6,000<br/>(2,000 reads; 4,000 writes) |
148-
| Two | 1,500 each | 1,000 each | 7,000<br/>(3,000 reads; 4,000 writes) |
149-
| Two | 1,000 each | 1,500 each | 8,000<br/>(2,000 reads; 6,000 writes) |
150-
| Three | 1,000 each | 1,000 each | 12,000<br/>(3,000 reads; 9,000 writes) |
152+
Because each instance needs the ability to write to every other instance, write operations significantly affect the total number of ops/sec.
153+
154+
Select a tab to see examples of throughput calculations for different Active-Active configurations.
155+
156+
{{< multitabs id="rc-aa-throughput-examples"
157+
tab1="Two regions, balanced between regions"
158+
tab2="Two regions, read/write heavy in one region"
159+
tab3="Three regions, balanced between regions"
160+
tab4="Three regions, different read/write in each region" >}}
161+
162+
For this database, we have two regions where read and write operations are balanced between the regions, as described in the table below:
163+
164+
| Region | Local read ops/sec | Local write ops/sec |
165+
|:------:|:------------------:|:-------------------:|
166+
| Region 1 | 2000 | 1000 |
167+
| Region 2 | 2000 | 1000 |
168+
169+
The total ops/sec for this database is calculated as follows:
170+
171+
```text
172+
Region 1 ops/sec = 2000 (local read) +
173+
1000 (local write) +
174+
1000 (write from Region 2) = 4000 ops/sec
175+
176+
Region 2 ops/sec = 2000 (local read) +
177+
1000 (local write) +
178+
1000 (write from Region 1) = 4000 ops/sec
179+
180+
Total ops/sec = 4000 (Region 1) + 4000 (Region 2)
181+
= 8000 ops/sec
182+
```
183+
184+
-tab-sep-
185+
186+
For this database, we have two regions where one region has more read and write operations than the other region, as described in the table below:
187+
188+
| Region | Local read ops/sec | Local write ops/sec |
189+
|:------:|:------------------:|:-------------------:|
190+
| Region 1 | 2000 | 1000 |
191+
| Region 2 | 4000 | 2000 |
192+
193+
The total ops/sec for this database is calculated as follows:
194+
195+
```text
196+
Region 1 ops/sec = 2000 (local read) +
197+
1000 (local write) +
198+
2000 (write from Region 2) = 5000 ops/sec
199+
200+
Region 2 ops/sec = 4000 (local read) +
201+
2000 (local write) +
202+
1000 (write from Region 1) = 7000 ops/sec
203+
204+
Total ops/sec = 5000 (Region 1) + 7000 (Region 2)
205+
= 12000 ops/sec
206+
```
207+
208+
-tab-sep-
209+
210+
For this database, we have three regions where read and write operations are balanced between the regions, as described in the table below:
211+
212+
| Region | Local read ops/sec | Local write ops/sec |
213+
|:------:|:------------------:|:-------------------:|
214+
| Region 1 | 2000 | 1000 |
215+
| Region 2 | 2000 | 1000 |
216+
| Region 3 | 2000 | 1000 |
217+
218+
The total ops/sec for this database is calculated as follows:
219+
220+
```text
221+
Region 1 ops/sec = 2000 (local read) +
222+
1000 (local write) +
223+
1000 (write from Region 2) +
224+
1000 (write from Region 3) = 5000 ops/sec
225+
226+
Region 2 ops/sec = 2000 (local read) +
227+
1000 (local write) +
228+
1000 (write from Region 1) +
229+
1000 (write from Region 3) = 5000 ops/sec
230+
231+
Region 3 ops/sec = 2000 (local read) +
232+
1000 (local write) +
233+
1000 (write from Region 1) +
234+
1000 (write from Region 2) = 5000 ops/sec
235+
236+
Total ops/sec = 5000 (Region 1) + 5000 (Region 2) + 5000 (Region 3)
237+
= 15000 ops/sec
238+
```
239+
240+
-tab-sep-
241+
242+
For this database, we have three regions where read and write operations are different between the regions, as described in the table below:
243+
244+
| Region | Local read ops/sec | Local write ops/sec |
245+
|:------:|:------------------:|:-------------------:|
246+
| Region 1 | 3000 | 1000 |
247+
| Region 2 | 4000 | 3000 |
248+
| Region 3 | 1000 | 2000 |
249+
250+
The total ops/sec for this database is calculated as follows:
251+
252+
```text
253+
Region 1 ops/sec = 3000 (local read) +
254+
1000 (local write) +
255+
3000 (write from Region 2) +
256+
2000 (write from Region 3) = 9000 ops/sec
257+
258+
Region 2 ops/sec = 4000 (local read) +
259+
3000 (local write) +
260+
1000 (write from Region 1) +
261+
2000 (write from Region 3) = 10000 ops/sec
262+
263+
Region 3 ops/sec = 1000 (local read) +
264+
2000 (local write) +
265+
1000 (write from Region 1) +
266+
3000 (write from Region 2) = 7000 ops/sec
267+
268+
Total ops/sec = 9000 (Region 1) + 10000 (Region 2) + 7000 (Region 3)
269+
= 26000 ops/sec
270+
```
271+
272+
{{< /multitabs >}}
151273

152274
For Search and query databases, the estimated throughput from the [Sizing calculator](https://redis.io/redisearch-sizing-calculator/) is the total amount of throughput you need. When setting throughput for your Active-Active database, use the total amount for each region and divide it depending on your read (query) and write (update) needs for each region. For example, if the total amount of throughput needed is 50000 ops/sec, you could set each region to have 20000 ops/sec for reads (queries) and 30000 ops/sec for writes (updates).
153275

content/operate/rc/security/access-control/access-management.md

Lines changed: 6 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -115,7 +115,7 @@ This table shows each role's ability to perform common tasks.
115115
|---|---|---|---|---|---|---|
116116
| Access management | <span title="Owners can manage account access">&#x2705; Yes</span> | <span title="Billing Admins may not manage account access">&#x274c; No</span> | <span title="Managers may not manage account access">&#x274c; No</span> | <span title="Members may not manage account access">&#x274c; No</span> | <span title="Viewers may not manage account access">&#x274c; No</span> | <span title="Logs Viewers may not manage account access">&#x274c; No</span> |
117117
| Account settings | <span title="Owners can change account settings">&#x2705; Yes</span> | <span title="Billing Admins can change the billing address in account settings">&#x2705; Yes<sup>[1](#table-note-1)</sup></span> | <span title="Managers may not manage account settings">&#x274c; No</span> | <span title="Members may not manage account settings">&#x274c; No</span> | <span title="Viewers may not manage account settings">&#x274c; No</span> | <span title="Logs Viewers may not manage account settings">&#x274c; No</span> |
118-
| Billing & payments | <span title="Owners can add/remove payment methods and view history">&#x2705; Yes</span> | <span title="Billing Admins can add/remove payment methods and view history">&#x2705; Yes</span> | <span title="Managers may not add/remove payment methods or view billing history (Managers may change subscription payment methods between those available to the account)">&#x274c; No</span> | <span title="Members may not add/remove payment methods or view billing history">&#x274c; No</span> | <span title="Viewers may not add/remove payment methods or view billing history">&#x274c; No</span> | <span title="Logs viewers may not add/remove payment methods or view billing history">&#x274c; No</span> |
118+
| Billing & payments | <span title="Owners can add/remove payment methods and view history">&#x2705; Yes</span> | <span title="Billing Admins can add/remove payment methods and view history">&#x2705; Yes</span> | <span title="Managers may not add/remove payment methods or view billing history (Managers may change subscription payment methods between those available to the account)">&#x274c; No<sup>[4](#table-note-4)</sup></span></span> | <span title="Members may not add/remove payment methods or view billing history">&#x274c; No</span> | <span title="Viewers may not add/remove payment methods or view billing history">&#x274c; No</span> | <span title="Logs viewers may not add/remove payment methods or view billing history">&#x274c; No</span> |
119119
| Create subscription | <span title="Owners can create new subscriptions">&#x2705; Yes</span> | <span title="Billing Admins may not create subscriptions">&#x274c; No</span> | <span title="Managers can create new subscriptions">&#x2705; Yes</span> | <span title="Members may not create subscriptions">&#x274c; No</span> | <span title="Viewers may not create subscriptions">&#x274c; No</span> | <span title="Logs viewers may not create subscriptions">&#x274c; No</span> |
120120
| Edit subscription | <span title="Owners can edit subscriptions">&#x2705; Yes</span> | <span title="Billing Admins can edit subscriptions to change the payment method">&#x2705; Yes<sup>[2](#table-note-2)</sup></span> | <span title="Managers can edit subscriptions">&#x2705; Yes</span> | <span title="Members may not edit subscriptions">&#x274c; No</span> | <span title="Viewers may not edit subscriptions">&#x274c; No</span> | <span title="Logs viewers may not edit subscriptions">&#x274c; No</span> |
121121
| Create database (affects cost) | <span title="Owners can create databases when doing so will impact costs">&#x2705; Yes</span> | <span title="Billing Admins may not create databases when doing so will impact costs">&#x274c; No</span> | <span title="Managers can create databases when doing so will impact costs">&#x2705; Yes</span> | <span title="Members may not create databases when doing so will impact costs">&#x274c; No</span> | <span title="Viewers may not create databases when doing so will impact costs">&#x274c; No</span> | <span title="Logs viewers may not create databases when doing so will impact costs">&#x274c; No</span> |
@@ -124,14 +124,16 @@ This table shows each role's ability to perform common tasks.
124124
| Edit database (no cost impact) | <span title="Owners can edit databases in ways that do not impact costs">&#x2705; Yes</span> | <span title="Billing Admins may not change databases in ways that do not affect costs">&#x274c; No</span> | <span title="Managers can change databases in ways that do not affect costs">&#x2705; Yes</span> | <span title="Members can change databases in ways that do not affect costs">&#x2705; Yes</span> | <span title="Viewers may not change databases in ways that do not affect costs">&#x274c; No</span> | <span title="Logs viewers may not change databases in ways that do not affect costs">&#x274c; No</span> |
125125
| View subscription | <span title="Owners can view subscription details">&#x2705; Yes</span> | <span title="Billing Admins can view subscription details">&#x2705; Yes</span> | <span title="Managers can view subscription details">&#x2705; Yes</span> | <span title="Members can view subscription details">&#x2705; Yes</span> | <span title="Viewers can view subscription details">&#x2705; Yes</span> | <span title="Logs viewers may not view subscriptions">&#x274c; No</span> |
126126
| View database | <span title="Owners can view database details">&#x2705; Yes</span> | <span title="Billing Admins can view the list of databases but not database details">&#x2705; Yes<sup>[3](#table-note-3)</sup></span> | <span title="Managers can view database details">&#x2705; Yes</span> | <span title="Members can view database details">&#x2705; Yes</span> | <span title="Viewers can view database details">&#x2705; Yes</span> | <span title="Logs viewers may not view databases">&#x274c; No</span> |
127-
| Use the [REST API]({{< relref "/operate/rc/api" >}}) | <span title="Owners can use the Redis Cloud API">&#x2705; Yes</span> | <span title="Billing Admins may not use the Redis Cloud API">&#x274c; No</span> | <span title="Managers may not use the REST API">&#x274c; No</span> | <span title="Members may not use the REST API">&#x274c; No</span> | <span title="Viewers can use the REST API for GET requests only">&#x2705; Yes<sup>[4](#table-note-4)</sup></span> | <span title="Logs viewers can use the REST API for GET /logs only">&#x2705; Yes<sup>[5](#table-note-5)</sup></span> |
127+
| Use the [REST API]({{< relref "/operate/rc/api" >}}) | <span title="Owners can use the Redis Cloud API">&#x2705; Yes</span> | <span title="Billing Admins may not use the Redis Cloud API">&#x274c; No</span> | <span title="Managers may not use the REST API">&#x274c; No</span> | <span title="Members may not use the REST API">&#x274c; No</span> | <span title="Viewers can use the REST API for GET requests only">&#x2705; Yes<sup>[5](#table-note-5)</sup></span> | <span title="Logs viewers can use the REST API for GET /logs only">&#x2705; Yes<sup>[6](#table-note-6)</sup></span> |
128128

129129
1. <a name="table-note-1" style="display: block; height: 80px; margin-top: -80px;"></a>Billing Admins can only edit the account billing address in Account Settings.
130130

131131
2. <a name="table-note-2" style="display: block; height: 80px; margin-top: -80px;"></a>Billing Admins can only change the payment method when editing a subscription.
132132

133133
3. <a name="table-note-3" style="display: block; height: 80px; margin-top: -80px;"></a>Billing Admins can see the list of databases, but can not see database details, including connection details.
134134

135-
4. <a name="table-note-4" style="display: block; height: 80px; margin-top: -80px;"></a>Viewers can use the REST API for GET requests, but can not modify subscription or database details.
135+
4. <a name="table-note-4" style="display: block; height: 80px; margin-top: -80px;"></a>Managers are able to view existing payment methods and assign them as payment methods for subscriptions, but they cannot add or remove payment methods.
136136

137-
5. <a name="table-note-5" style="display: block; height: 80px; margin-top: -80px;"></a>Logs viewers can only use the [`GET logs/`]({{< relref "/operate/rc/api/api-reference#tag/Account/operation/getAccountSystemLogs" >}}) endpoint of the REST API.
137+
5. <a name="table-note-5" style="display: block; height: 80px; margin-top: -80px;"></a>Viewers can use the REST API for GET requests, but cannot modify subscription or database details.
138+
139+
6. <a name="table-note-6" style="display: block; height: 80px; margin-top: -80px;"></a>Logs viewers can only use the [`GET logs/`]({{< relref "/operate/rc/api/api-reference#tag/Account/operation/getAccountSystemLogs" >}}) endpoint of the REST API.

0 commit comments

Comments
 (0)