Error trying to scale Azure Cache for Redis

Question

I'm trying to scale Azure Cache for Redis, but I'm getting the following error:
The resource '/subscriptions/*****/resourceGroups/****/providers/Microsoft.Cache/Redis/***' is busy processing a previous update request or is a system maintenance. As such, it is currently unable to accept the update request. Please try again later. RequestID=5f8f4d51-837d-4b88-9d7a-2c1877a5f042

If I try to force a reboot, I can't do it either.

Answer 1

Hi @Milton Camara , welcome to Microsoft Q&A forum and sorry for the trouble you are facing. This could be intermittent issue because of any parallel process.

Can you please check the schedule updates settings if any updates were planned in the period you were trying to scale up? You can check it from left menu Settings -> Schedule Updates.

Also, if possible please provide the region and current vs new azure Redis Cache Size you are trying to update to. I will try to replicate to confirm if this is generic or specific issue.

Answer 2

@Milton Camara , sorry that you ran into this issue. As documented below, this error indicates that a management operation on the cache (like scale) has failed and further cache management operations are blocked until the cache status is restored. Please note that the cache will be fully functional and available for all data commands during this time. If you are still facing this issue, please reach out to Azure support to help unblock management operations on your cache.
https://learn.microsoft.com/en-us/azure/azure-cache-for-redis/cache-monitor-troubleshoot-faq#why-am-i-seeing--cache-is-busy-processing-a-previous-update-request-or-is-undergoing-system-maintenance--as-such--it-is-currently-unable-to-accept-the-update-request--please-try-again-later--

Answer 3

I experienced this same error when trying to upgrade my cache from version 4 to version 6. Tried multiple times over 3 days and got the same error every time.

I then tried again 4 days later and the operation succeeded without issue, so I thought I should share my experience that this issue may go away after several days.