Document OOM requirements for geo-replication#128433
Document OOM requirements for geo-replication#128433chantalolieman wants to merge 1 commit intoMicrosoftDocs:mainfrom
Conversation
Added note about OOM conditions affecting geo-replication sync.
|
@chantalolieman : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
|
Learn Build status updates of commit 0b7f16a: ✅ Validation status: passed
For more details, please refer to the build report. |
There was a problem hiding this comment.
Pull request overview
Note
Copilot was unable to run its full agentic suite in this review.
Documents an additional operational condition (out-of-memory) that can pause geo-replication sync, so customers can diagnose “unhealthy” replication states more accurately.
Changes:
- Added a bullet describing how OOM pauses geo-replication synchronization.
- Added mitigation guidance (TTLs / eviction policy) to reduce memory pressure.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
|
||
| - 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. |
There was a problem hiding this comment.
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.
| - 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. |
|
|
||
| - 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. |
There was a problem hiding this comment.
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.
|
@chantalolieman This pull request was opened in the public repo. PMs should work in the private repo, per the Microsoft Docs contributor guide. We can keep this PR open for review and merge, but would you make future content updates in the private repo? Thank you! @flang-msft Could you take a look? |
Added note about OOM conditions affecting geo-replication sync.