On two-node Qdrant cluster Network traffic growth or query timeout after increasing replica sharding
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 34.7k
- Forks
- 2.7k
- Avg merge
- 1d 18h
- Merged PRs (30d)
- 187
Description
one：Increasing shards leads to network traffic growth
origin collection info：2shard 1replica，ecs network 5M
migrate： create collection init_from: old collection to 6shard 1replica，ecs network 5M*6
so,what problem?
two: Increasing replica leads to query timeout
origin collection info：2shard 1replica，ecs network 5M
migrate： create collection init_from: old collection to 6shard 2replica，query timeout
so,what problem?
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
No files or tests are named. Start by reproducing the two-node Qdrant scenarios using collection creation with init_from, increasing shards from 2 to 6 and replicas from 1 to 2 while observing network traffic and query timeouts. Done means explaining the observed behavior and identifying the affected subsystem or a confirmed fix path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- databases, distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100