Skip to content

Commit 3825507

Browse files
committed
DOC-5567 Feedback update to remove override option from the adjust availability lag tolerance threshold section and change the section to focus on changing the default only
1 parent d76d617 commit 3825507

File tree

1 file changed

+7
-13
lines changed

1 file changed

+7
-13
lines changed

content/operate/rs/monitoring/db-availability.md

Lines changed: 7 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -49,22 +49,16 @@ If the local database endpoint is unavailable, returns an error status code and
4949

5050
The database availability API supports lag-aware availability checks that consider replication lag tolerance. 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.
5151

52-
### Adjust availability lag tolerance threshold
52+
### Change default availability lag tolerance threshold
5353

54-
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:
54+
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.
5555

56-
- 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.
56+
To change the default threshold for the entire cluster, set `availability_lag_tolerance_ms` with an [update cluster]({{<relref "/operate/rs/references/rest-api/requests/cluster#put-cluster">}}) request:
5757

58-
```sh
59-
PUT /v1/cluster
60-
{ "availability_lag_tolerance_ms": 100 }
61-
```
62-
63-
- 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">}}).
64-
65-
```sh
66-
GET /v1/bdbs/<database_id>/availability?extend_check=lag&availability_lag_tolerance_ms=100
67-
```
58+
```sh
59+
PUT /v1/cluster
60+
{ "availability_lag_tolerance_ms": 100 }
61+
```
6862
6963
### Lag-aware database availability checks
7064

0 commit comments

Comments
 (0)