It was not possible to connect to the redis server(s); to create a disconnected multiplexer

It was not possible to connect to the redis server(s); to create a disconnected multiplexer

I have the following piece of code to connect to azure redis cache.
   public class CacheConnectionHelper
    {
        private static Lazy lazyConnection = new Lazy(() =>
        {
            return ConnectionMultiplexer.Connect(SettingsHelper.AzureRedisCache);
        });

        public static ConnectionMultiplexer Connection
        {
            get
            {
                return lazyConnection.Value;
            }
        }
    }

And I use it this way
public static List GetModules()
        {
            IDatabase cache = CacheConnectionHelper.Connection.GetDatabase();
            List listOfModules = new List();
            listOfModules = (List)cache.Get("ApplicationModules");
            if (listOfModules == null)
            {
                listOfModules = dbApp.Modulos.ToList();
                cache.Set("ApplicationModules", listOfModules, TimeSpan.FromMinutes(SettingsHelper.CacheModuleNames));
                return listOfModules;
            }
            else {
                return listOfModules;
            }
        }

However 1 or 2 times per day I get this exception:
 Additional information: It was not possible to connect to the redis server(s); to create a disconnected multiplexer, disable AbortOnConnectFail. UnableToResolvePhysicalConnection on PING

The question is how can I refactor this code to go to the database in case the cache connection fails?

Solutions/Answers:

Answer 1:

The error you are getting is usually a sign that you have not set abortConnect=false in your connection string. The default value for abortConnect is true, which makes it so that StackExchange.Redis won’t reconnect to the server automatically under some conditions. We strongly recommend that you set abortConnect=false in your connection string so that SE.Redis will auto-reconnect in the background if a network blip occurs.

Answer 2:

for beginners who dive in other’s code an face this problem:

if (RedisConn == null)
        { 
            ConfigurationOptions option = new ConfigurationOptions
            {
                AbortOnConnectFail = false,
                EndPoints = { redisEndpoint }
            };
            RedisConn = ConnectionMultiplexer.Connect(option);
        }

Answer 3:

This problem was solved in a new release, the version 1.2.6 – you can see in Here

Answer 4:

For those maintaining older codebases, you may run into “It was not possible to connect to the redis server(s); to create a disconnected multiplexer, disable AbortOnConnectFail. UnableToResolvePhysicalConnection on PING”

Once I upgraded to a more recent nuget package the error was still present but I got more error information: “The client and server cannot communicate, because they do not possess a common algorithm”.

Once I applied the registry keys mentioned here I was ok. For those that don’t wish to make that global change I believe there has been a PR for a setting.

Answer 5:

You should also pay attention to the last part of your error message, as it seems to provide very useful details about the reason why connection have failed.

In your case:

It was not possible to connect to the redis server(s); to create a disconnected multiplexer, disable AbortOnConnectFail. UnableToResolvePhysicalConnection on PING

My case:

It was not possible to connect to the redis server(s); to create a disconnected multiplexer, disable AbortOnConnectFail. Timeout

Our Awesome Tools

References

Related:  WPF borderless window with shadow VS2012 style