Skip to content

Conversation

@jeffswenson
Copy link
Collaborator

This change enables the crud writer by default for IMMEDIATE and VALIDATED mode LDR jobs.

Release note: LDR now supports partial indexes and is tolerant of mismatched column ids in the source and destination tables.

Epic: CRDB-51533

@jeffswenson jeffswenson requested a review from a team as a code owner November 5, 2025 13:15
@jeffswenson jeffswenson requested review from kev-cao and msbutler and removed request for a team November 5, 2025 13:16
@cockroach-teamcity
Copy link
Member

This change is Reviewable

Copy link
Collaborator

@stevendanna stevendanna left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's Goooooo!

Release note: LDR now supports partial indexes and is tolerant of mismatched column ids in the source and destination tables.

Talk about under-selling things :D.

This change enables the crud writer by default for IMMEDIATE and
VALIDATED mode LDR jobs.

Release note: LDR now supports partial indexes and is tolerant of
mismatched column ids in the source and destination tables.

Epic: CRDB-51533
@jeffswenson jeffswenson force-pushed the jeffswenson-enable-crud-writer branch from b6da592 to 0d92aa9 Compare November 5, 2025 13:33
Copy link
Collaborator

@msbutler msbutler left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Horay!!!

@jeffswenson
Copy link
Collaborator Author

Thanks for the reviews!

bors r+

craig bot pushed a commit that referenced this pull request Nov 5, 2025
156935: logical: enable crud writer by default r=jeffswenson a=jeffswenson

This change enables the crud writer by default for IMMEDIATE and VALIDATED mode LDR jobs.

Release note: LDR now supports partial indexes and is tolerant of mismatched column ids in the source and destination tables.

Epic: CRDB-51533

156939: gossip: fix gossip.callbacks.pending_duration time metric r=pav-kv a=stevendanna

In 32723e5 I reversed this subtraction somehow.

Release note (bug fix): Fix bug that could result in incorrect gossip.callbacks.pending_duration metric value being recorded.

Co-authored-by: Jeff Swenson <jeffswenson@betterthannull.com>
Co-authored-by: Steven Danna <danna@cockroachlabs.com>
@craig
Copy link
Contributor

craig bot commented Nov 5, 2025

Build failed (retrying...):

craig bot pushed a commit that referenced this pull request Nov 5, 2025
155033: asim: use kvserver.LoadBasedRebalancingObjective r=wenyihu6 a=wenyihu6

Previously, LBRebalancingObjective was part of the simulation settings, using
QPS as the load rebalance objective. However, the cluster setting
kvserver.LoadBasedRebalancingObjective defaults to CPU rebalancing instead. This
commit updates asim to rely on the cluster setting, adopting the default cluster
setting configuration.

Epic: CRDB-55052
Release note: none 
Resolves: #154512

156594: backup: test adding/dropping database in cluster backup and restore r=jeffswenson a=msbutler

Epic: None

Release note: none

156876: rttanalysis: deflake BenchmarkJobs r=rafiss a=rafiss

The benchmark started failing since the code doesn't handle a nil table descriptor. The fix is to create a dummy descriptor in the job payload details.

fixes #151302
Release note: None

156935: logical: enable crud writer by default r=jeffswenson a=jeffswenson

This change enables the crud writer by default for IMMEDIATE and VALIDATED mode LDR jobs.

Release note: LDR now supports partial indexes and is tolerant of mismatched column ids in the source and destination tables.

Epic: CRDB-51533

156942: server: make mma Allocator calls more visible r=wenyihu6 a=tbg

They were kind of hidden before, and it has been
tripping me up every now and then for a while.
The problem was that NewAllocatorState returns
a private struct directly, so a bunch of the
calls later in the method do not show up when
you look at the call hierarchy for the Allocator
interface. This is now fixed.

Epic: CRDB-55052.

156943: workflow: backport stale action should mark PRs stale after 14 days r=RaduBerinde a=rail

Previously, the backport stale action marked PRs as stale after 21 days of inactivity. This change updates the configuration to mark PRs as stale after 14 days of inactivity, ensuring that stale backport PRs are identified and addressed more promptly.

Epic: none
Release note: none

Co-authored-by: wenyihu6 <wenyi@cockroachlabs.com>
Co-authored-by: Michael Butler <butler@cockroachlabs.com>
Co-authored-by: Rafi Shamim <rafi@cockroachlabs.com>
Co-authored-by: Jeff Swenson <jeffswenson@betterthannull.com>
Co-authored-by: Tobias Grieger <tobias.b.grieger@gmail.com>
Co-authored-by: Rail Aliiev <rail@iqchoice.com>
@craig
Copy link
Contributor

craig bot commented Nov 5, 2025

Build failed (retrying...):

@craig
Copy link
Contributor

craig bot commented Nov 5, 2025

@craig craig bot merged commit 40c6169 into cockroachdb:master Nov 5, 2025
24 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants