Skip to content

release-26.1: changefeedccl: fix min_checkpoint_frequency=0 regression#164892

Merged
andyyang890 merged 1 commit intocockroachdb:release-26.1from
andyyang890:backport26.1-164765
Mar 5, 2026
Merged

release-26.1: changefeedccl: fix min_checkpoint_frequency=0 regression#164892
andyyang890 merged 1 commit intocockroachdb:release-26.1from
andyyang890:backport26.1-164765

Conversation

@andyyang890
Copy link
Copy Markdown
Collaborator

@andyyang890 andyyang890 commented Mar 5, 2026

Backport 1/1 commits from #164765.

/cc @cockroachdb/release


In adfa889, we advertently made it
so that setting min_checkpoint_frequency to 0 would cause the changefeed's
highwater to not advance/not send resolved timestamps. This patch fixes that.

Fixes #164866

Release note (bug fix): In a recent change that was included in 25.4+,
we inadvertently made it so that setting min_checkpoint_frequency to
0 would cause the changefeed's highwater to not advance/not send
resolved timestamps. This bug has been fixed. Note however that setting
min_checkpoint_frequency to lower than 500ms is not recommended as
it may cause degraded changefeed performance.


Release justification: fixes regression of existing functionality

In adfa889, we advertently made it
so that setting `min_checkpoint_frequency` to 0 would cause the changefeed's
highwater to not advance/not send resolved timestamps. This patch fixes that.

Release note (bug fix): In a recent change that was included in 25.4+,
we inadvertently made it so that setting `min_checkpoint_frequency` to
0 would cause the changefeed's highwater to not advance/not send
resolved timestamps. This bug has been fixed. Note however that setting
`min_checkpoint_frequency` to lower than `500ms` is not recommended as
it may cause degraded changefeed performance.
@blathers-crl
Copy link
Copy Markdown

blathers-crl bot commented Mar 5, 2026

Thanks for opening a backport.

Before merging, please confirm that the change does not break backwards compatibility and otherwise complies with the backport policy. Include a brief release justification in the PR description explaining why the backport is appropriate. All backports must be reviewed by the TL for the owning area. While the stricter LTS policy does not yet apply, please exercise judgment and consider gating non-critical changes behind a disabled-by-default feature flag when appropriate.

@blathers-crl blathers-crl bot added backport Label PR's that are backports to older release branches T-cdc labels Mar 5, 2026
@cockroach-teamcity
Copy link
Copy Markdown
Member

This change is Reviewable

}

cdcTest(t, testFn)
}
Copy link
Copy Markdown
Collaborator Author

@andyyang890 andyyang890 Mar 5, 2026

Choose a reason for hiding this comment

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

Merge conflict is from this branch not having TestCoreChangefeedProgress after this test in this file

@andyyang890 andyyang890 requested a review from jeffswenson March 5, 2026 03:31
@andyyang890 andyyang890 marked this pull request as ready for review March 5, 2026 03:31
@andyyang890 andyyang890 requested a review from a team as a code owner March 5, 2026 03:31
Copy link
Copy Markdown
Collaborator

@jeffswenson jeffswenson left a comment

Choose a reason for hiding this comment

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

LGTM

@andyyang890 andyyang890 merged commit fdeaecd into cockroachdb:release-26.1 Mar 5, 2026
22 checks passed
@andyyang890 andyyang890 deleted the backport26.1-164765 branch March 5, 2026 13:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport Label PR's that are backports to older release branches T-cdc target-release-26.1.2

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants