Planning support for Sentinel with Redis?

[IngGiorgioBernardi]

With CacheManager 3.0, I'm trying to use a connection string to Redis configuring 3 Sentinel nodes instead of direct Redis connection.
I see that CacheManger can't handle the changes of mastership: when the master node breaks down, and a new master is elected by Sentinel, my application continues connecting to the previous master showing the following message:

The message timed out in the backlog attempting to send because no connection became available (5000ms) - Last Connection Exception: It was not possible to connect to the redis server(s). ConnectTimeout, command=PING, timeout: 5000, inst: 0, qu: 0, qs: 0, aw: False, bw: CheckingForTimeout, rs: NotStarted, ws: Initializing, in: 0, last-in: 0, cur-in: 0, sync-ops: 0, async-ops: 2, serverEndpoint: PREVIOUSMASTER:6379, conn-sec: n/a, aoc: 0, mc: 1/1/0, mgr: 10 of 10 available, clientName: CLIENTHOST(SE.Redis-v2.8.24.3255), IOCP: (Busy=0,Free=1000,Min=1,Max=1000), WORKER: (Busy=0,Free=32767,Min=6,Max=32767), POOL: (Threads=7,QueuedItems=0,CompletedItems=67486,Timers=95), v: 2.8.24.3255 (Please take a look at this article for some common client-side issues that can cause timeouts: https://stackexchange.github.io/StackExchange.Redis/Timeouts)

You can see that it is still trying to connect to previous Redis master using the redis port (not Sentinel port I've configured in the connection string).
The connection string I'm using is:

serviceName=myservice,OTHERNODE:26379,PREVIOUSMASTER:26379,NEWMASTER:26379,allowAdmin=true,connectTimeout=2000,abortConnect=false

Is there any plan to integrate Sentinel's behaviour? Or is there something I'm doing wrong?
Thanks

[MichaConrad]

I'm pretty sure this has nothing todo with CacheManager, you'd have to look into the StackExchange:Redis docu of how that handles sentinels.
I remember I tested that at least a bit a long long time ago, and I got it working with failing over and such. But I'm sorry I don't remember how exactly you have to configure that ;)

:hint: You can pass in a pre-configured multiuplexer to CacheManager in case the configuration via connection string isn't enough.