Based on StackExchange. Redis sentry pattern implementation of a distributed cache, using the AspNetCore. HealthChecks. Redis for health test, when the primary node failure after health check will not automatically replace new master node, The result of health inspection is always Unhealthy.

[ZerekZhang]

Based on StackExchange. Redis sentry pattern implementation of a distributed cache, using the AspNetCore. HealthChecks. Redis for health test, when the primary node failure after health check will not automatically replace new master node, The result of health inspection is always Unhealthy,
Stackexchange. Redis configuration connection string: "127.0.0.1:26379,127.00 0.1:26380,127.00 0.1:26381, SSL = false, sslHost = null, connectTimeout = 4000, allowAdmin = true, defaultDatab ase=7,password=123456,serviceName=mymaster"
What happened:

What you expected to happen:

How to reproduce it (as minimally and precisely as possible):

Source code sample:

Anything else we need to know?:

Environment:

• .NET Core version
  net5.0
• Healthchecks version
  AspNetCore.HealthChecks.Redis :5.0.2
• Operative system:
• Others:

[sungam3r]

Please format your connection string.

[ZerekZhang]

Please format your connection string.

formatted

[bdas-tsla]

Hi Team, are there any updates on this yet.

[sungam3r]

Nope.