Skip to content

Commit cc88d86

Browse files
committed
added links to images
1 parent 276025e commit cc88d86

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

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

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ ms.author: franlanglois
1010
---
1111
# How to administer Azure Cache for Redis
1212

13-
This article describes how to do administration tasks such as [rebooting](#reboot) and [scheduling updates](#schedule-updates) for your Azure Cache for Redis instances.
13+
This article describes how to do administration tasks such as [rebooting](#reboot) and [Update channel and Schedule updates](#update-channel-and-schedule-updates) for your Azure Cache for Redis instances.
1414

1515
[!INCLUDE [updated-for-az](../../includes/updated-for-az.md)]
1616

@@ -78,19 +78,20 @@ No. Reboot isn't available for the Enterprise tier yet. Reboot is available for
7878

7979
## Flush data (preview)
8080

81-
On the left, **Flush** allows you to delete or flush all data in your cache and is supported by Basic, Standard and Premium tiers. This Flush capability can be used before scaling operations to potentially reduce the time required to complete scaling operation on your cache. You can also configure to run the Flush operation periodically on your dev/test caches to keep memory usage in check.
81+
When using th Basic, Standard, or Premium tiers of Azure Cache for Redis, you see **Flush data** on the resource menu. The **Flush data** operation allows you to delete or _flush_ all data in your cache. This _flush_ operation can be used before scaling operations to potentially reduce the time required to complete the scaling operation on your cache. You can also configure to run the _flush_ operation periodically on your dev/test caches to keep memory usage in check.
82+
8283
The _flush_ operation, when executed on a clustered cache, clears data from all shards at the same time.
8384

8485
> [!IMPORTANT]
8586
> Previously, the _flush_ operation was only available for geo-replicated Enterprise tier caches. Now, it is available in Basic, Standard and Premium tiers.
8687
>
87-
<!--> Need screenshot here <-->
88+
:::image type="content" source="media/cache-administration/cache-flush.png" alt-text="Screenshot showing flush data selected in the resource menu of a cache instance. ":::
8889

8990
## Update channel and Schedule updates
9091

91-
On the left, **Schedule updates** allows you to choose an update channel and a maintenance window for your cache instance.
92+
On the left, **Schedule updates** allows you to choose an update channel and a maintenance window for your cache instance.
9293

93-
Any cache instance using the **Stable** update channel receives updates a few weeks later than cache instances using **Preview** update channel. We recommend choosing the **Preview** update channel for your non-production and less critical workloads. Choose the **Stable** update channel for your most critical, production workloads. All caches default to the **Stable** update channel by default.
94+
Any cache instance using the **Stable** update channel receives updates a few weeks later than cache instances using **Preview** update channel. We recommend choosing the **Preview** update channel for your non-production and less critical workloads. Choose the **Stable** update channel for your most critical, production workloads. All caches default to the **Stable** update channel by default.
9495

9596
> [!IMPORTANT]
9697
> Changing the update channel on your cache instance results in your cache undergoing a patching event to apply the right updates. Consider changing the update channel during your maintenance window.
@@ -103,7 +104,6 @@ A maintenance window allows you to control the days and times of a week during w
103104
>
104105
Currently, no option is available to configure an update channel or scheduled updates for an Enterprise tier cache.
105106

106-
<!-->Need to update this screenshot.<-->
107107
:::image type="content" source="media/cache-administration/redis-schedule-updates-2.png" alt-text="Screenshot showing schedule updates":::
108108

109109
To specify a maintenance window, check the days you want and specify the maintenance window start hour for each day. Then, select **OK**. The maintenance window time is in UTC and can only be configured on an hourly basis.

0 commit comments

Comments
 (0)