StackExchange / StackExchange/StackExchange.Redis
IPv6 Cluster connection errors
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 6.2k
- Forks
- 1.6k
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 43
Description
I've got an IPv6 only Redis cluster. The client connects fine to any hash slots on the existing node, but if it needs to go to another node it fails. Have proven the network is fine as another client will connect fine not in .Net code. Odd how the port is in the endpoint.
Connection string was "[abcd:1234:3:a::a]:7000,[abcd:1234:3:a::b]:7000"
The GetEndpoints has 8 endpoints when there is only 6 in the cluster (3 master, 3 slave).
'Endpoint [abcd:1234:3:a::c:7000]:0 serving hashslot 6438 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. IOCP:
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 with the ConnectionMultiplexer handling of the IPv6 connection string and the GetEndpoints result for a Redis cluster. Reproduce the six-node IPv6-only cluster case using the supplied endpoint format, then trace the endpoint reported for hashslot 6438. Done means redirects to other cluster nodes connect successfully and GetEndpoints reports the expected nodes without malformed ports.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, redis
- Domain
- databases, distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100