StackExchange / StackExchange/StackExchange.Redis
Redis Cluster: Endpoint 10.42.241.4:6379 serving hashslot 1643 is not reachable at this point of time.
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 6.2k
- Forks
- 1.6k
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 43
Description
Using Redis clustered with 6 nodes, 3 master and 3 slave. In our production environment we sometimes get this error. About 1 or 2 a week.
Endpoint 10.42.241.4:6379 serving hashslot 1643 is not reachable at this point of time. Please check connectTimeout value. If it is low, try increasing it to give the ConnectionMultiplexer a chance to recover from the network disconnect.
The endpoint is up and running with many connections and no signs of having gone down. On average, all three masters are processing about 30-60 commands per second. The application and the Redis cluster are all running in Rancher Kubernetes within the same namespace.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by investigating the intermittent Redis Cluster connectivity error involving ConnectionMultiplexer and the connectTimeout setting in the described six-node Kubernetes deployment. Reproduce or correlate the hashslot 1643 failures with endpoint availability and network conditions; done means identifying a reproducible cause and a clearly scoped change or documented configuration fix.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, redis
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100