-
Notifications
You must be signed in to change notification settings - Fork 3.7k
Closed
Labels
area/balanceIssues or PRs related to data balanceIssues or PRs related to data balancekind/fixCategorizes issue or PR as related to a bug.Categorizes issue or PR as related to a bug.
Description
Describe the bug
When decommission BE, some of tablets may has lots of replicas generated by clone task.
Why
Give examples of why:
- Tablet X has 3 replicas on A, B, C 3 BEs.
- C is decommission, so we choose the Backend D to relocating the new replica,
- After relocating, Tablet X has 4 replicas: A, B, C(decommision), D(may be version incomplete)
- D may be version incomplete because the clone task ran a long time, the new version has been published.
- At the next time of tablet checking, Tablet X's status is still REPLICA_RELOCATING.
If we don't choose D as dest BE to do the new relocating, it will choose new backend E
to store the new replicas. So back and forth, the number of replicas will increase forever.
So a better solution is to select D as dest BE again to do the clone task. This may trigger an increment clone task
that can be done more fast.
Metadata
Metadata
Assignees
Labels
area/balanceIssues or PRs related to data balanceIssues or PRs related to data balancekind/fixCategorizes issue or PR as related to a bug.Categorizes issue or PR as related to a bug.