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
153538: roachtest: deflake disk-full roachtest r=RaduBerinde a=jbowens
This is a speculative fix for a disk-full roachtest failure. This roachtest induces an out-of-disk scenario on a node and ensures that removing the automatic emergency ballast allows recovery. In #153445 it appears disk space is exhausted on the node, but the node never notices because the write workload is insufficient to trigger any write I/O to new pages. This commit adjusts the disk-full roachtest's workload to run a little longer (10m vs 4m) and to write larger-sized values (512-byte) to ensure we continue to write a nontrivial volume of data after we intentionally exhaust available disk space.
Epic: none
Fixes: #153445.
Release note: none
153583: sql/schemachanger: fix index creation failures after pause/resume r=fqazi a=fqazi
Previously, when the index backfiller was tracking completed spans, the final chunk of a span would cause an update to be emitted that incorrectly indicated the entire span was complete. While this was not an issue with a single ingest goroutine, it caused problems with the introduction of multiple ingest goroutines. As a result, if the job was paused and resumed after this incorrect progress update, the backfiller could skip rows, leading to validation errors. To address this, this patch ensures that progress updates for the final chunk of a span correctly report only the work completed in that chunk.
Fixes: #153522
Release note (bug fix): Addressed a bug where index creation could fail due to validation errors if the schema change was retried or paused/resumed during the backfill.
153589: kvnemesis: correctly handle errors from DeleteRangeUsingTombstoneOperation r=miraradeva a=stevendanna
Previously we were initializing the result in the
DeleteRangeUsingTombstoneOperation case using the err variable that had been set to nil.
Now, we correctly using the Err from the result. While here, I've also re-arranged the code so that the cases are a bit more consistent.
Epic: none
Release note: None
Co-authored-by: Jackson Owens <[email protected]>
Co-authored-by: Faizan Qazi <[email protected]>
Co-authored-by: Steven Danna <[email protected]>
0 commit comments