13 comments (13 comments)0 reactions (0 reactions)0 assignees (0 assignees)Go12,459 stars (12,459 stars)2,681 forks (2,681 forks)batch import
help wantedtodo
Description
1、Codis3.1中etcd作为协调器时是否可以考虑使用V3?v2在使用watch时会有丢失数据的风险
Contributor guide
- Tech stack
- go
- Domain
- backendinfrastructure
- Issue type
- feature
- DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
- 4
- Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
- over 1 week
- Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
- stale
- ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
- mostly clear
- Prerequisites
- Go programmingetcd basicsCodis architecture
- Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
- 10
- Research direction
- Investigate the current usage of etcd v2 in Codis's coordinator code (likely in the coordinator package). Review the etcd client library and watch implementation to confirm data loss risk. Determine the feasibility of upgrading to etcd v3, including API changes and migration steps. Check if any dependencies or configuration changes are required. Examine existing comments and discussions in the issue for additional insights.