-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
storage: don't down-replicate the range holding range lease #7918
Conversation
Review status: 0 of 3 files reviewed at latest revision, 3 unresolved discussions, all commit checks successful. storage/replicate_queue.go, line 165 [r1] (raw file):
We should be using storage/replicate_queue.go, line 167 [r1] (raw file):
Rather than checking afterwards, an alternative approach would be to strip the lease holder from the list of replicas passed to storage/replicate_queue.go, line 168 [r1] (raw file):
Comments from Reviewable |
Review status: 0 of 6 files reviewed at latest revision, 3 unresolved discussions, some commit checks pending. storage/replicate_queue.go, line 165 [r1] (raw file):
|
Review status: 0 of 6 files reviewed at latest revision, all discussions resolved, some commit checks failed. Comments from Reviewable |
Reviewed 2 of 3 files at r1, 4 of 4 files at r2. Comments from Reviewable |
918d7f5
to
fb98911
Compare
This won't matter once cockroachdb#7904 is in, but there's no need to use Desc() if we're already locked.
This is the preventative measure for stopping a down-replication of the range lease holder's replica. RemoveTarget will pick the worst replica from the list that does not contain the lease holder's replica. Part of cockroachdb#5737
This is the preventative measure for stopping a down-replication of the range
lease holder's replica. RemoveTarget will pick the worst replica from the list
that does not contain the lease holder's replica.
Part of #5737
This change is