Skip to content

Document OOM requirements for geo-replication #128433

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

Open
chantalolieman wants to merge 1 commit into
base: main
Choose a base branch
from
+2 −0
Open

Document OOM requirements for geo-replication #128433

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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 articles/redis/how-to-active-geo-replication.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -241,6 +241,8 @@ To monitor the _Geo Replication Healthy_ metric in the Azure portal:

- Large key size - Large keys can create synchronization issues among geo-replicas. To maintain smooth performance and reliable replication, we recommend keeping key sizes under 500MB when using geo-replication. If individual key size gets close to 2GB the cache faces geo-replication health issues.

- OOM - Some free memory is needed for the geo-replication sync to work. When the cache is OOM, syncing will be paused. Make sure to reduce memory pressure by setting TTLs or changing the eviction policy.
Copy link

Copilot AI Apr 22, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The term “OOM” may be unclear in docs without expansion, and “When the cache is OOM” is ambiguous (OOM kill vs. memory full). Consider expanding to “out of memory (OOM)” and clarifying the condition (for example, memory pressure / maxmemory reached) under which geo-replication sync pauses.

Suggested change
- OOM - Some free memory is needed for the geo-replication sync to work. When the cache is OOM, syncing will be paused. Make sure to reduce memory pressure by setting TTLs or changing the eviction policy.
- Out of memory (OOM) - Some free memory is needed for geo-replication sync to work. When the cache is under memory pressure or has reached its memory limit, syncing is paused. Reduce memory pressure by setting TTLs or changing the eviction policy.

Copilot uses AI. Check for mistakes.
Copy link

Copilot AI Apr 22, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There’s a trailing space at the end of the line, which can cause markdown linting/style checks to fail or create unintended formatting. Remove the trailing whitespace.

Copilot uses AI. Check for mistakes.

### Flush caches using Azure CLI or PowerShell

The Azure CLI and PowerShell can also be used to trigger a flush operation. For more information on using Azure CLI, see [az redisenterprise database flush](/cli/azure/redisenterprise#az-redisenterprise-database-flush). For more information on using PowerShell, see [Invoke-AzRedisEnterpriseCacheDatabaseFlush](/powershell/module/az.redisenterprisecache/invoke-azredisenterprisecachedatabaseflush).
Expand Down