Azure Cache for Redis: Unable to connect, unable to reboot

Question

Reboot attempt via Azure Portal:
One or more shards of cache '...' failed with error: 'The resource '/subscriptions/[...]/resourceGroups/[...]/providers/Microsoft.Cache/Redis/[...]' 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=134710d4-b7f7-4d60-8a90-d8d325458b07'

No health related issues found. View resource health dashboard
No changes to this resource in the last 72 hours. View change details
No recent patch operations were found
No recent failovers were found
This cache did not have its IP changed recently.
No recent performance issues were detected
This is not a Basic tier cache

Connection attempt via an app:
StackExchange.Redis.RedisConnectionException: SocketFailure on EVAL

I have had these types of problems in the past, but they usually resolved themselves within a few hours. Is there any way to fix this, besides recreating the resource as in [1]?

[1] https://learn.microsoft.com/en-us/answers/questions/703459/error-when-try-to-access-reboot-or-scale-cache-for.html

Answer 1

Hi @Johannes Binder ,

Welcome to Microsoft Q&A platform and thanks for using Azure Services.

Sorry that you ran into this issue.
As per the documentation, this error indicates that a management operation on the cache (like scaling/patching) 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.

May I know if you have a support plan to raise support ticket?

Answer 2

Hi @ShaktiSingh-MSFT , thanks for the response! Unfortunately I cannot confirm the information in the documentation, as stated above. I don't have a support plan as I simply want to report a technical issue on Azure's side (that is how it looks like to me) or a workaround for thereof.

Answer 3

Hi @ShaktiSingh-MSFT , thanks a lot for your support! I eventually switched to an alternative resource for about two days. Also i created a ticket for that kind of issues.