Skip to content

Commit 9798936

Browse files
Merge pull request #222282 from MSFTeegarden/flush-command-update
Update cache-configure.md
2 parents 3cc54b3 + 5db6f2c commit 9798936

File tree

2 files changed

+9
-0
lines changed

2 files changed

+9
-0
lines changed

articles/azure-cache-for-redis/cache-configure.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -546,6 +546,11 @@ Configuration and management of Azure Cache for Redis instances is managed by Mi
546546
- SLAVEOF
547547
- SYNC
548548

549+
For cache instances using active geo-replication, the following commands are also blocked to prevent accidental data loss:
550+
551+
- FLUSHALL
552+
- FLUSHDB
553+
549554
> [!IMPORTANT]
550555
> Because configuration and management of Azure Cache for Redis instances is managed by Microsoft, some commands are disabled. The commands are listed above. If you try to invoke them, you receive an error message similar to `"(error) ERR unknown command"`.
551556

articles/azure-cache-for-redis/cache-how-to-active-geo-replication.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -19,6 +19,10 @@ Active geo-replication groups up to five instances of Enterprise Azure Cache for
1919
> Data transfer between Azure regions is charged at standard [bandwidth rates](https://azure.microsoft.com/pricing/details/bandwidth/).
2020
>
2121
22+
> [!IMPORTANT]
23+
> The FLUSHALL and FLUSHDB commands are blocked when using active geo-replication to prevent accidental data loss across replicated cache instances.
24+
>
25+
2226
## Create or join an active geo-replication group
2327

2428
1. When creating a new Azure Cache for Redis resource, select the **Advanced** tab. Complete the first part of the form including clustering policy. For more information on choosing **Clustering policy**, see [Clustering Policy](quickstart-create-redis-enterprise.md#clustering-policy).

0 commit comments

Comments
 (0)