redis主从切换次数多的时候找不到主结点
Open
- Dominant language
- Java
- Stars
- 5.6k
- Forks
- 1.1k
- PR merge metrics
- No merged PRs in 30d
Description
使用jetcache做redis缓存,当redis通过哨兵选举主从节点切换次数达到三次的时候就没办法写,可以读,也就是主节点找不到,读可以通过从节点来读,报错的信息是主节点未知,是否是配置有误呢
`Master is currently unknown: [RedisMasterSlaveNode [redisURI=RedisURI [host='xx.xx.xx.xx', port=6379], role=SLAVE], RedisMasterSlaveNo
`
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing the Redis Sentinel setup and reproducing three master-slave switches with JetCache. Use the reported “Master is currently unknown” error as the starting point, then determine whether the configuration or master discovery is responsible. Done means writes continue to work after repeated failovers and the cause is documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, redis
- Domain
- backend, databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100