Skip to content

Commit

Permalink
doc(1.8.0): add replica auto-balance to best-practice
Browse files Browse the repository at this point in the history
Signed-off-by: Chin-Ya Huang <chin-ya.huang@suse.com>
  • Loading branch information
c3y1huang committed Sep 20, 2024
1 parent 125ff12 commit 279e099
Showing 1 changed file with 10 additions and 0 deletions.
10 changes: 10 additions & 0 deletions content/docs/1.8.0/best-practices.md
Original file line number Diff line number Diff line change
Expand Up @@ -217,3 +217,13 @@ This setting should be set to `false` in production environment to ensure the be
> Recommend: `false`
This setting should be set to `false` in production environment to ensure every volume have the best availability when created. Because with the setting set to `true`, the volume creation won't error out even there is only enough room to schedule one replica. So there is a risk that the cluster is running out of the spaces but the user won't be made aware immediately.

### Replica Auto-Balance

> Recommend: `least-effort`
For production environments, we recommend to set Replica Auto-Balance to `least-effort`. This setting ensures that at least one replica is placed on a different node and in each zone, providing extra high availablity (HA).

Check failure on line 225 in content/docs/1.8.0/best-practices.md

View workflow job for this annotation

GitHub Actions / codespell

availablity ==> availability

In certain edge cases, you might consider using the `best-effort`, which continuously attempts to evenly distribute replicas across nodes and zones. However, this setting can lead to frequent rebuilds if the cluster is unstable.

For most users, having multiple replicas without Replica Auto-Balance setting is sufficient to achieve basic HA, especially if you prefer to avoid excessive rebuilds.

0 comments on commit 279e099

Please sign in to comment.