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
154276: sql/inspect: add checkpointing tracking to INSPECT r=spilchen a=spilchen
Previously, INSPECT jobs did not support checkpointing, meaning job restarts would reprocess all data from the beginning. This change adds span based checkpointing to allow jobs to resume from their last completed spans.
Progress is tracked using jobfrontier to store completed spans. On job restart, the resumer loads completed spans and filters them from the work to be done.
Closes#148297
Release note: None
Epic: CRDB-30356
154391: kv: make TestFollowerReadsWithStaleDescriptor work with multi-tenancy r=stevendanna a=arulajmani
This previously didn't work for a slew of reasons, commented in-line.
References #142800
Release note: None
154404: kvcoord: treat non-transactional writes as non-idempotent r=stevendanna a=miraradeva
Previously, non-transactional requests were treated as idempotent by the `DistSender`, meaning they were retried in the presence of RPC errors. This could lead to double-evaluating these requests, including writes. This can result in, for example, an increment applying twice, or more subtle problems like a blind write evaluating twice, overwriting another unrelated write that fell in-between. This issue is known and documented in the `DistSender` code. It is not a production correctness issue since SQL always uses the transactional KV API.
This commit treats non-transactional write batches the same way as transactional batches that contain a commit: if they experience an RPC error, they should not be retried, and should return an ambiguous error. The new logic is currently behind an off-by-default cluster setting as it will require deflaking many tests. The plan is to enable this in some kvnemesis tests first.
Informs: #154389
Informs: #114814
Release note: None
154557: colcontainer: harden ctx capture in diskQueueWriter r=yuzefovich a=yuzefovich
In ffb4666 we added more memory accounting to the disk queue. This required capturing the context inside the `diskQueueWriter` in order to preserve the `io.Writer` signature. We just saw a test failure where this capture was problematic - it's possible that when we close the disk queue as a whole (which happens _after_ closing all operators) that the captured context contains the tracing span that has been finished (since the relevant operator has already been closed). To go around this issue we now update the captured context before finishing each file.
An alternative solution could've been to use `context.Background` since we only need the context object for memory accounting purposes (in a single `Resize` call) so losing some contextual information there doesn't seem like a big deal.
Fixes: #154347.
Release note: None
Co-authored-by: Matt Spilchen <[email protected]>
Co-authored-by: Arul Ajmani <[email protected]>
Co-authored-by: Mira Radeva <[email protected]>
Co-authored-by: Yahor Yuzefovich <[email protected]>
0 commit comments