Share via

Error when try to access, reboot, or scale Cache for Redis

Dusty H 1 Reputation point
2022-01-20T18:06:42.753+00:00

Resource Health = Available - There aren't any known Azure platform problems affecting this Redis Cache.
Diagnose & Solve - Patching diagnostic = No recent patch operation found
Diagnose & Solve - Failover diagnostics = No recent failover found
Diagnose & Solve - Performance diagnostics = No recent performance problem detected

Application fails to reach Cache, and reboot or scale requests result in an error like this:

Rebooting cache failed
One or more shards of cache '[resource name (redacted)]' failed with error: 'The resource '/subscriptions/[subscription ID (redacted)]/resourceGroups/CallDataTransfer/providers/Microsoft.Cache/Redis/[resource name (redacted)]' 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.
RequestID=87673e15-8e56-4342-8b78-167efec9b2d0'

This has been out of service since before today (1/20/22) at 7AM EST. What can I do?

Azure Cache for Redis
Azure Cache for Redis
An Azure service that provides access to a secure, dedicated Redis cache, managed by Microsoft.
219 questions
0 comments

4 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Oury Ba-MSFT 16,886 Reputation points Microsoft Employee
    2022-01-20T22:04:28.287+00:00

    Hi @Dusty H Thank you for posting your Question on Microsoft Q&A.

    Please check the below point if none of those apply to your case then please try again.

    Operations that are not supported
    You can't scale to or from a Premium cache.

    You can't change from a Standard to a Basic cache.

    You can scale from a Basic cache to a Standard cache but you can't change the size at the same time. If you need a different size, you can do a subsequent scaling operation to the desired size.

    You can scale up from a C0 (250 MB) cache to a larger size, but you can't scale a larger size down to a C0 cache.

    If a scaling operation fails, the service will try to revert the operation and the cache will revert to the original size.

    Please let me know the result.

    Regards,
    Oury

    0 comments
  2. Dusty H 1 Reputation point
    2022-01-20T22:08:31.3+00:00

    The attempt was to scale from Basic to Standard in attempt to improve availability. This was attempted after application access failed and reboot failed with the error previously mentioned. This error is still occurring now if I try to reboot.

  3. Dusty H 1 Reputation point
    2022-01-26T17:29:04.307+00:00

    It was still producing the same errors as of yesterday, but I was able to delete it. I moved my application to a new instance on 1/20 and that one has been working fine.

  4. ShrutiPathak-MSFT 81 Reputation points Microsoft Employee
    2022-01-26T20:24:36.387+00:00

    Hi @Dusty H , sorry that you ran into this issue and had to recreate your cache. 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. 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--