Skip to content

Commit a796b46

Browse files
committed
removed no context link to gist
1 parent d56c0a0 commit a796b46

File tree

2 files changed

+7
-13
lines changed

2 files changed

+7
-13
lines changed

articles/azure-cache-for-redis/cache-troubleshoot-data-loss.md

Lines changed: 3 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ description: Learn how to resolve data-loss problems with Azure Cache for Redis,
55

66

77
ms.topic: conceptual
8-
ms.date: 12/01/2021
8+
ms.date: 03/05/2025
99
---
1010

1111
# Troubleshoot data loss in Azure Cache for Redis
@@ -58,8 +58,6 @@ expired_keys:46583
5858
db0:keys=3450,expires=2,avg_ttl=91861015336
5959
```
6060

61-
This resource provides details on using `keyspace` notifications or `MONITOR` to debug these types of issues. For information about using diagnostic metrics to see if there's a correlation between when the key went missing and a spike in expired keys, see the Appendix of [Debugging Redis Keyspace Misses](https://gist.github.com/JonCole/4a249477142be839b904f7426ccccf82#appendix).
62-
6361
### Key eviction
6462

6563
Azure Cache for Redis requires memory space to store data. It purges keys to free up available memory when necessary. When the **used_memory** or **used_memory_rss** values in the [INFO](https://redis.io/commands/info) command approach the configured **maxmemory** setting, Azure Cache for Redis starts evicting keys from memory based on [cache policy](https://redis.io/topics/lru-cache).
@@ -122,11 +120,10 @@ Caches in the Standard and Premium tiers offer much higher resiliency against da
122120

123121
Consider using [Redis data persistence](https://redis.io/topics/persistence) and [geo-replication](./cache-how-to-geo-replication.md) to improve protection of your data against these infrastructure failures.
124122

125-
## Additional information
126-
127-
These articles provide more information on avoiding data loss:
123+
## Related Content
128124

129125
- [Troubleshoot Azure Cache for Redis server-side issues](cache-troubleshoot-server.md)
130126
- [Choosing the right tier](cache-overview.md#choosing-the-right-tier)
131127
- [Monitor Azure Cache for Redis](monitor-cache.md)
132128
- [How can I run Redis commands?](cache-development-faq.yml#how-can-i-run-redis-commands-)
129+
- [Sample code for examining keyspace notifications](https://gist.github.com/JonCole/0d6205b4771e5c803bc1e085517484a2#file-rediskeyspacenotificationsexample-cs)

articles/azure-cache-for-redis/managed-redis/managed-redis-troubleshoot-data-loss.md

Lines changed: 4 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ ms.service: azure-managed-redis
77
ms.custom:
88
- ignite-2024
99
ms.topic: conceptual
10-
ms.date: 11/15/2024
10+
ms.date: 03/05/2025
1111
---
1212

1313
# Troubleshoot data loss in Azure Managed Redis (preview)
@@ -59,7 +59,7 @@ expired_keys:46583
5959
db0:keys=3450,expires=2,avg_ttl=91861015336
6060
```
6161

62-
62+
You can examine the diagnostic metrics for your cache to see if there's a correlation between when the key went missing and a spike in evicted keys.
6363

6464
### Key eviction
6565

@@ -73,8 +73,6 @@ You can monitor the number of evicted keys by using the [INFO](https://redis.io/
7373
evicted_keys:13224
7474
```
7575

76-
You can also look at diagnostic metrics for your cache, to see if there's a correlation between when the key went missing and a spike in evicted keys. See the Appendix of [Debugging Redis Keyspace Misses](https://gist.github.com/JonCole/4a249477142be839b904f7426ccccf82#appendix) for information about using keyspace notifications or **MONITOR** to debug these types of issues.
77-
7876
### Key deletion
7977

8078
Redis clients can issue the [DEL](https://redis.io/commands/del) or [HDEL](https://redis.io/commands/hdel) command to explicitly remove keys from Azure Managed Redis. You can track the number of delete operations by using the [INFO](https://redis.io/commands/info) command. If **DEL** or **HDEL** commands have been called, they'll be listed in the `Commandstats` section.
@@ -118,11 +116,10 @@ Redis is an in-memory data store. Data is kept on the physical or virtual machin
118116

119117
Consider using [Redis data persistence](https://redis.io/topics/persistence) and [geo-replication](../cache-how-to-geo-replication.md) to improve protection of your data against these infrastructure failures.
120118

121-
## Additional information
122-
123-
These articles provide more information on avoiding data loss:
119+
## Related content
124120

125121
- [Troubleshoot Azure Managed Redis server-side issues](managed-redis-troubleshoot-server.md)
126122
- [Choosing the right tier](managed-redis-overview.md#choosing-the-right-tier)
127123
- [Monitor Azure Managed Redis](../monitor-cache.md)
128124
- [How can I run Redis commands?](managed-redis-development-faq.yml#how-can-i-run-redis-commands-)
125+
- [Sample code for examining keyspace notifications](https://gist.github.com/JonCole/0d6205b4771e5c803bc1e085517484a2#file-rediskeyspacenotificationsexample-cs)

0 commit comments

Comments
 (0)