Work on creation time of Redis Cache
The time of creating a Redis Cache is to long. It should be improved
Thank you for your feedback. This is on our backlog
Sivakumar Sankararaman commented
28 minutes for C3 in east us , better than others looks like some improvement ??
Andrew Falk commented
For those adding Redis with VNet integration, be aware of all the NSG requirements. If you don't have them all in place you will wait 60-120 minutes only to see a failure message of 'conflict'. There really should be a better error message. Or better yet, report on the missing rules before making us wait 2 hours for the failure.
Here is link to the NSG requirements:
6 year backlog LOL
The only "new" idea I have is for everyone tweet a link to this issue and hastag #LoECDA
At the moment, it seems they are the only ones who can help. I guess this issue just needs more visibility?
Cong Hau Nguyen Viet commented
Any update on this.???. I've wait for hours... with 2 failed times...and no redis cache created :-/
Samuel Njogu commented
This is still taking too long, for an item already registered on your backlog almost 6 years ago today.
Any updates Azure team? THis is the most requested feature in this category and yet you are not doing any actions.
Tommi Hovi commented
I waited for hour and half for the deployment @ westeurope. The API then returned an error and redis instance was not created. Frustrating. I'm working with Terraform like Josiah.
Come on Microsoft, 5 years?
Armaan Dhaliwal-McLeod commented
We need to prioritize this. Many customers are complaining about long deployment times for this particular service(much longer than any other service available). I've tried this myself and even just deploying a simple Standard C1 size takes about 30 min to deploy.
Any updates Azure?
Patrick Ecker commented
Our whole ARM deployment would take 5min, but then there is Redis Cache: 20-30min @ west europe
mumtaz khan commented
its better to create redis in container :) - Microsoft please do something .
Josiah Berkebile commented
Have to echo this concern. In our Terraform deployment of our job orchestrator which uses Redis, all of the Azure resources get created in 5 minutes or less, and then we are left waiting for another 15-20 minutes for Redis Cache to finish coming online. It's the same for the destruction of the infrastrucutre, as well - we can destroy all of our Azure resources in under 5 minutes, except Redis Cache takes again 15-20 minutes. This really slows down development on our Terraform infrastructure scripting.
About 20 minutes to create a redis in France Central ! Please do something !
You competitor GCP in Belgium is able to start a redis instance in less than 5 minutes.
Paul Vrugt commented
this is ridiculous. Creating a redis cache as part of ARM deployment brings our deployement to a screeching halt. How can this still be an issue after more that 5 years?
Redis Cache in 2020 create in West Europe it will take approximate 35 to 40 minutes
Farukh Sharipov commented
West US still 5 years latter and I am waiting on my 27th minute for Azure Redis to be created..
Ryan Byrne (Europe) commented
France Central, standard redis cache (C1) - Just under 40 mins to deploy via Terraform.
To echo everyone else this is really hampering deployment patterns.
Alexander Trauzzi commented
These start times are unreasonable. Move this service to linux and pass down some savings. I do not understand why you would run redis on Windows?!