milvus-io/milvus

[Feature]: Add retry for etcd operation

Closed

#17,569 opened on Jun 15, 2022

View on GitHubContributor guide
 (3 comments) (0 reactions) (1 assignee)Go (4,000 forks)batch import
good first issuekind/feature

Repository metrics

Stars
 (44,298 stars)
PR merge metrics
 (Avg merge 7d) (314 merged PRs in 30d)

Description

Is there an existing issue for this?

  • I have searched the existing issues

Is your feature request related to a problem? Please describe.

Milvus highly rely on etcd for meta operation. Retry is need since failed to operate on etcd may cause server crash. To be noticed, the CompareValueAndSwap, CompareVersionAndSwap may no be able to add retry in a no brainer style so we need to take care about it.

Describe the solution you'd like.

No response

Describe an alternate solution.

No response

Anything else? (Additional Context)

No response

Contributor guide

Research direction
Implement retry logic for etcd operations in Milvus. Pay special attention to CompareValueAndSwap and CompareVersionAndSwap as they require careful handling to avoid inconsistent states. Use exponential backoff and limit retries.
Tech stack
go
Domain
backenddatabase
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
Go
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30