StackExchange / StackExchange/StackExchange.Redis
Using Configuration Endpoint to Connect AWS Elasticcache for REDIS
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 6.2k
- Forks
- 1.6k
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 43
Description
I have an Elasticache instance running in cluster mode with one shard with three nodes (1 primary, 2 replicas) in different AZs.
Our Redis Client code uses StackExchange REDIS Library to connect AWS Elasticache for REDIS. We use the AWS Elasticache configuration endpoint (not the specific node endpoint) while connecting it. According to the AWS Documentation, the Configuration Endpoint will be updated with the new primary after the failover is completed. Here are my questions
Does the StackExchange REDIS Library leverage AWS Elasticache Configuration Endpoint to handle the routing of the requests to the right Primary?
Or
Does StackExcahge REDIS library auto-discover (using INFO commands) the primary & secondary endpoints and make a connection to the correct Primary? How does it behave after the failover?
Can you please help us to understand?
@NickCraver @mgravell
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
The payload names no repository files, tests, or entry points. Start by reviewing the AWS ElastiCache configuration endpoint documentation and StackExchange.Redis connection behavior; done means documenting whether the client discovers primary and replica endpoints and how failover is handled.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, redis
- Domain
- databases, documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100