Skip to content

Commit d7f3566

Browse files
Update data-eviction-policies.md
1 parent 7ab596d commit d7f3566

File tree

1 file changed

+1
-9
lines changed

1 file changed

+1
-9
lines changed

content/operate/rc/databases/configuration/data-eviction-policies.md

Lines changed: 1 addition & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -45,7 +45,7 @@ Auto Tiering can extend your database across RAM and Flash Memory and intelligen
4545
When using Active-Passive replication with [Replica Of]({{< relref "/operate/rs/databases/import-export/replica-of/" >}}), data eviction and expiration policies have important implications for data consistency.
4646

4747
{{< warning >}}
48-
**Do not write to the destination (passive) replica database.** Writing to the destination replica can cause serious data consistency issues and replication failures.
48+
**Do not write to the destination (passive) replica database.** Writing to the destination replica can cause data consistency issues and replication failures.
4949
{{< /warning >}}
5050

5151
### Problems caused by writing to passive replicas
@@ -56,13 +56,5 @@ In Active-Passive setups, eviction and expiration only operate on the active (so
5656
- **Data inconsistency**: Local writes create differences between the source and destination databases, causing replicated commands to behave differently on each database.
5757
- **Replication failures**: Inconsistent data can cause replicated commands to fail with errors, which will cause the synchronization process to exit and break replication.
5858

59-
### Transitioning from passive to active
60-
61-
To properly transition a passive replica to become an active, writable database:
62-
63-
1. **Stop replication** using the Redis Cloud console interface
64-
2. **Remove the replicaOf source** by running the `REPLICAOF NO ONE` command on the database
65-
66-
Both steps are required to ensure the database can safely accept writes and manage its own eviction and expiration policies.
6759

6860

0 commit comments

Comments
 (0)