Skip to content

K8s: add BD level HA note #2079

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Sep 3, 2025
+2 −0
Merged

K8s: add BD level HA note #2079

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
4da055f
add BD level HA note
kaitlynmichael Sep 3, 2025
1ae0427
Update content/operate/rs/databases/configure/replica-ha.md
kaitlynmichael Sep 3, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions content/operate/rs/databases/configure/replica-ha.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -110,6 +110,8 @@ By default, replica HA has a 10-minute grace period after node failure and befor

{{<note>}}The default grace period is 30 minutes for containerized applications using [Redis Enterprise Software for Kubernetes]({{< relref "/operate/kubernetes/" >}}).{{</note>}}

{{<note>}}For Kubernetes deployments, if ReplicaHA (previously SlaveHA) is enabled at the cluster level, you must also manually enable it at the database level for each RedisEnterpriseDatabase (REDB) using the UI or `rladmin`. Without manual database-level configuration, databases will show `slave_ha: disabled (database)` even when cluster-level ReplicaHA is enabled.{{</note>}}

To configure this grace period from rladmin, run:

``` text
Expand Down