StackExchange / StackExchange/StackExchange.Redis

[FEAT] server selection with availability_zone awareness support

Open
#2,983 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C#
Stars
6.2k
Forks
1.6k
Avg merge
1d 15h
Merged PRs (30d)
43

Description

Some servers (valkey) will reply with availability_zone in the HELLO reply.

It would be nice (for pure latency overhead), to always attempt to connect to servers in the same zone as the client.

Usefully when running a cluster with multiple shards where each share has a replica in each zone.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the code that parses the Redis HELLO reply and the code that selects servers for clustered shards. Check how availability_zone could be retained for the client and compared with server zones. Done means same-zone servers are preferred when available, with existing selection behavior preserved when zone information is absent.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp, redis
Domain
databases, distributed-systems
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.