Commit 06edb41
committed
kvserver: don't proceed with unsafe replication changes after 10s
`within10s` is called from within the change replicas txn as a last layer
of defense against replication changes that would lose quorum. While looking
into cases in which precisely this happened, I wondered why this last line
of defense couldn't block these ill-advised changes.
It turns out that within10s had a bug: it would return without an error.
In effect, it wasn't doing anything except delay the problematic change.
This bug is mine - introduced almost five years ago in #57564. Consequently,
it's present in "all" versions of CockroachDB.
Release note(bug fix): A mechanism that blocks replication changes that would
result in a loss of quorum was ineffective. It now works as intended.1 parent b97d3b3 commit 06edb41
1 file changed
+3
-0
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
2402 | 2402 | | |
2403 | 2403 | | |
2404 | 2404 | | |
| 2405 | + | |
| 2406 | + | |
| 2407 | + | |
2405 | 2408 | | |
2406 | 2409 | | |
2407 | 2410 | | |
| |||
0 commit comments