You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
147168: colexecdisk: propagate DiskFull errors as expected r=yuzefovich a=yuzefovich
We just saw a sentry report that was issued due to InternalError raised after Dequeue'ing from a disk queue. It's not clear what the error was (since it was redacted), but it might have been a DiskFull error. We already have special handling for it on the Enqueue path, but the Dequeue path can also trigger this error (on the first call to Dequeue after some Enqueue calls - in order to flush the buffered batches), so this commit audits all disk queue methods to use the helper for error propagation.
The only place where we do disk usage accounting is `diskQueue.writeFooterAndFlush`, so I traced which methods could end up calling it (both Enqueue and Dequeue, but also Close) and their call sites - this is how the affected places were chosen. Additionally, I didn't want to introduce the error propagation via panics if it wasn't there already, so one spot wasn't modified.
Fixes: #147132.
Release note: None
157847: bench/rttanalysis: shard TestBenchmarkExpectation to avoid timeouts r=rafiss a=rickystewart
Re-apply `9fecc53b0b3cde307b5379ee5b88fae0fc8f34e2`, but add a `skip` if the test is running under `s390x`.
Release note: none
Epic: none
157868: testcluster: assign unique ClusterName r=RaduBerinde,stevendanna a=pav-kv
This commit makes `TestCluster` by default assign a unique cluster name in the `TestServerArgs`. The cluster name is shared by all participating or added nodes, unless overridden in the per-node args.
This helps preventing accidental message exchange between `TestCluster`s in the same environment that use the same TCP port in close proximity from each other.
Addresses #157838
157930: mma: fix a couple of todos related to changes r=wenyihu6 a=sumeerbhola
- subsumesChanges no longer needs the prev state as a parameter, since subsumption is only a function of the observed state and expected next state. The existing comparison with prev.IsLeaseholder was unnecessary and flawed.
- Removed the todo around the panic in applyReplicaChange, since the expectation is that the range and store must exist. The callers are responsible for ensuring that. There was an old flawed idea that we would try to add the range at this point in the code, which we had long abandoned, but never removed from the code comment.
Epic: CRDB-55052
Release note: None
Co-authored-by: Yahor Yuzefovich <[email protected]>
Co-authored-by: Ricky Stewart <[email protected]>
Co-authored-by: Pavel Kalinnikov <[email protected]>
Co-authored-by: sumeerbhola <[email protected]>
0 commit comments