Skip to content

Commit 17bb777

Browse files
committed
Merge branch 'patch-77' of https://github.com/Amrinder-Singh29/azure-docs into fxl---Update-cache-how-to-scale-112573
2 parents c9d9e2c + 7ca8941 commit 17bb777

File tree

1 file changed

+6
-1
lines changed

1 file changed

+6
-1
lines changed

articles/azure-cache-for-redis/cache-how-to-scale.md

Lines changed: 6 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -270,6 +270,7 @@ The following list contains answers to commonly asked questions about Azure Cach
270270
- [After scaling, do I have to change my cache name or access keys?](#after-scaling-do-i-have-to-change-my-cache-name-or-access-keys)
271271
- [How does scaling work?](#how-does-scaling-work)
272272
- [Do I lose data from my cache during scaling?](#do-i-lose-data-from-my-cache-during-scaling)
273+
- [Can I use all the features of Premium tier after scaling?](#can-i-use-all-the-features-of-premium-tier-after-scaling)
273274
- [Is my custom databases setting affected during scaling?](#is-my-custom-databases-setting-affected-during-scaling)
274275
- [Is my cache be available during scaling?](#is-my-cache-be-available-during-scaling)
275276
- [Are there scaling limitations with geo-replication?](#are-there-scaling-limitations-with-geo-replication)
@@ -316,6 +317,10 @@ No, your cache name and keys are unchanged during a scaling operation.
316317
- When you scale a **Basic** cache to a **Standard** cache, the data in the cache is typically preserved.
317318
- When you scale a **Standard**, **Premium**, **Enterprise**, or **Enterprise Flash** cache to a larger size, all data is typically preserved. When you scale a Standard or Premium cache to a smaller size, data can be lost if the data size exceeds the new smaller size when it's scaled down. If data is lost when scaling down, keys are evicted using the [allkeys-lru](https://redis.io/topics/lru-cache) eviction policy.
318319

320+
### Can I use all the features of Premium tier after scaling?
321+
322+
No, features that are creation level settings in Premium tier such as configuring of VNET, setting up zone redundancy won't be available for configuration after scaling. You need to create a new instance in case you are looking to leverage any of those features.
323+
319324
### Is my custom databases setting affected during scaling?
320325

321326
If you configured a custom value for the `databases` setting during cache creation, keep in mind that some pricing tiers have different [databases limits](cache-configure.md#databases). Here are some considerations when scaling in this scenario:
@@ -454,4 +459,4 @@ Unlike Basic, Standard, and Premium tier caches, Enterprise and Enterprise Flash
454459
## Next steps
455460

456461
- [Configure your maxmemory-reserved setting](cache-best-practices-memory-management.md#configure-your-maxmemory-reserved-setting)
457-
- [[Best practices for scaling](cache-best-practices-scale.md)]
462+
- [Best practices for scaling](cache-best-practices-scale.md)

0 commit comments

Comments
 (0)