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/release-notes/rs-8-0-releases/rs-8-0-tba.md
+18-4Lines changed: 18 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ categories:
6
6
- operate
7
7
- rs
8
8
compatibleOSSVersion: Redis 7.4.0
9
-
description: Redis Open Source 8.0 and 8.2 features. Lag awareness API. Metrics stream engine GA.
9
+
description: Redis Open Source 8.0 and 8.2 features. Lag-aware availability API. Metrics stream engine GA.
10
10
linkTitle: 8.0.0-tba (September 2025)
11
11
weight: 90
12
12
---
@@ -19,7 +19,7 @@ This version offers:
19
19
20
20
- Redis Open Source 8.0 and 8.2 features
21
21
22
-
- Lag awareness API
22
+
- Lag-aware availability API
23
23
24
24
- Metrics stream engine GA
25
25
@@ -63,9 +63,23 @@ Redis Open Source 8.0 and 8.2 features are now available when you [create]({{<re
63
63
64
64
- See [What's new in Redis 8.2]({{<relref "/develop/whats-new/8-2">}}) and [Redis Open Source 8.2 release notes]({{<relref "/operate/oss_and_stack/stack-with-enterprise/release-notes/redisce/redisos-8.2-release-notes">}}) for more details.
65
65
66
-
#### Lag awareness API
66
+
#### Lag-aware availability API
67
67
68
-
TBA
68
+
The [database availability API]({{<relref "/operate/rs/references/rest-api/requests/bdbs/availability">}}) now supports lag-aware availability checks that consider replication lag tolerance.
69
+
70
+
You can reduce the risk of data inconsistencies during disaster recovery by incorporating lag-aware availability checks into your disaster recovery solution and ensuring failover-failback flows only occur when databases are accessible and sufficiently synchronized.
71
+
72
+
The lag tolerance threshold is 100 milliseconds by default. Depending on factors such as workload, network conditions, and throughput, you might want to adjust the lag tolerance threshold using one of the following methods:
73
+
74
+
- Change the default threshold for the entire cluster by setting `availability_lag_tolerance_ms` with an [update cluster]({{<relref "/operate/rs/references/rest-api/requests/cluster#put-cluster">}}) request.
75
+
76
+
- Override the default threshold by adding the `availability_lag_tolerance_ms` query parameter to specific lag-aware [availability checks]({{<relref "/operate/rs/references/rest-api/requests/bdbs/availability">}}). For example:
77
+
78
+
```sh
79
+
GET /v1/bdbs/<database_id>/availability?extend_check=lag&availability_lag_tolerance_ms=100
80
+
```
81
+
82
+
For more details, see [Check database availability for monitoring and load balancers]({{<relref "/operate/rs/monitoring/db-availability">}}).
0 commit comments