Skip to content

Conversation

andyyang890
Copy link
Collaborator

This patch fixes a bug where the progress skew metrics could show
incorrect data because the computation previously relied on comparing
the fastest span/table timestamps with the checkpointed timestamp
(overall resolved timestamp) and these two pieces of information
weren't kept in sync.

Fixes #155083

Release note: None

This patch fixes a bug where the progress skew metrics could show
incorrect data because the computation previously relied on comparing
the fastest span/table timestamps with the checkpointed timestamp
(overall resolved timestamp) and these two pieces of information
weren't kept in sync.

Release note: None
@cockroach-teamcity
Copy link
Member

This change is Reviewable

@andyyang890 andyyang890 added the backport-25.4.x Flags PRs that need to be backported to 25.4 label Oct 10, 2025
@andyyang890 andyyang890 requested a review from log-head October 10, 2025 20:41
@andyyang890 andyyang890 marked this pull request as ready for review October 10, 2025 20:41
@andyyang890 andyyang890 requested a review from a team as a code owner October 10, 2025 20:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport-25.4.x Flags PRs that need to be backported to 25.4

Projects

None yet

Development

Successfully merging this pull request may close these issues.

changefeedccl: table skew metric can be non-zero when per-table tracking is off

2 participants