-
Notifications
You must be signed in to change notification settings - Fork 3.7k
[Bug][TabletRepair] Fix bug that too many replicas generated when decommission BE #4148
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
kangkaisen
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1, LGTM
|
Rebase to solve the conflict. |
kangkaisen
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1
|
Sorry that this solution still has problem, I will fix it in this PR after testing in our product env. |
…ommission BE Try to select the BE with an existing replicas as the destination BE for REPLICA_RELOCATING clone task.
| // 1. PUSH finished in BE but failed or not yet report to FE | ||
| // 2. repair for VERSION_INCOMPLETE finished in BE, but failed or not yet report to FE | ||
| replica.updateVersionInfo(backendVersion, backendVersionHash, dataSize, rowCount); | ||
| replica.setBad(false); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For reviewer:
In the original design logic, when the status of a replica is bad, it cannot become not bad again.
This is a clerical error and will cause the admin set replica status function to fail.
kangkaisen
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1
…ommission BE (apache#4148) Try to select the BE with an existing replicas as the destination BE for REPLICA_RELOCATING clone task. Fix apache#4147 Also add 2 new FE configs `max_clone_task_timeout_sec` and `min_clone_task_timeout_sec` Change-Id: I948a54bacfd5ba9045fdccecfb44b04f0fda75b7
…ommission BE (apache#4148) Try to select the BE with an existing replicas as the destination BE for REPLICA_RELOCATING clone task. Fix apache#4147 Also add 2 new FE configs `max_clone_task_timeout_sec` and `min_clone_task_timeout_sec`
…counter fdb txn conflict when mow load get ms delete bitmap lock (apache#52360) (apache#4148) pick apache#52360
Proposed changes
Try to select the BE with an existing replicas as the destination BE for
REPLICA_RELOCATING clone task.
Fix #4147
Also add 2 new FE configs
max_clone_task_timeout_secandmin_clone_task_timeout_secTypes of changes
Checklist
Put an
xin the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.