StackExchange / StackExchange/StackExchange.Redis
How hard would it be to group/multiplex a MGET across the cluster slots?
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 6.2k
- Forks
- 1.6k
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 43
Description
Was not even thinking about it when I started to explore, but normally MGET is not supported on a cluster. But I know at least a few situations where it's now support in clients like Lettuce(?) I think.
Thinking quickly without knowing the innards!! Breaks up a single MGET into an MGET per cluster shard, based on grouping the keys by shard they end up in? Doesn't sound too nasty, but again ideas/thoughts from those who know this better would be good!!
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 reading the issue and the repository’s Redis cluster and MGET entry points, then compare how keys are assigned to cluster shards. Determine whether grouping keys into one MGET per shard is supported by the client’s current design; done would require an agreed approach and validation that clustered MGET requests work correctly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, redis
- Domain
- backend-api-design, databases, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100