StackExchange / StackExchange/StackExchange.Redis
Adding slave to sentinel results in failed queries
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 6.2k
- Forks
- 1.6k
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 43
Description
Hi guys!
I was expecting to be able to add more slaves on the fly when using sentinel, but as soon as I do queries get directed to them.
I have verified that the configuration doesn't include min-slaves-max-lag so the default value should be used.
Does your library ignore this option and queries all available slaves regardless of status?
Please note I am using an older version, 2.6.80 , as we are using the windows port of redis from forever ago.
Will upgrading solve this issue?
Thanks in advance!
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 report concerns Redis Sentinel queries after adding replicas while using StackExchange.Redis 2.6.80, but names no source file, test, or entry point. First reproduce the behavior with the reported version and Sentinel setup, then compare it with an upgrade; done means determining whether replica eligibility is handled correctly and documenting the result.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, redis
- Domain
- database
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100