Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

release-24.1: changefeedccl: bump franz-go dependency to fix deadlock #132785

Merged
merged 1 commit into from
Oct 17, 2024

Conversation

asg0451
Copy link
Contributor

@asg0451 asg0451 commented Oct 16, 2024

Backport 1/1 commits from #132761.

/cc @cockroachdb/release

Release justification: fix deadlock during changefeed shutdown.


Bump the version of franz-go to get a fix for an
issue where it could deadlock on client shutdown.

Fixes: #132198

Release note (bug fix): The franz-go library has
been updated to fix a potential deadlock on changefeed restarts.

Bump the version of franz-go to get a fix for an
issue where it could deadlock on client shutdown.

Fixes: cockroachdb#132198

Release note (bug fix): The franz-go library has
been updated to fix a potential deadlock on changefeed restarts.
@asg0451 asg0451 requested a review from a team as a code owner October 16, 2024 19:52
Copy link

blathers-crl bot commented Oct 16, 2024

Thanks for opening a backport.

Please check the backport criteria before merging:

  • Backports should only be created for serious
    issues
    or test-only changes.
  • Backports should not break backwards-compatibility.
  • Backports should change as little code as possible.
  • Backports should not change on-disk formats or node communication protocols.
  • Backports should not add new functionality (except as defined
    here).
  • Backports must not add, edit, or otherwise modify cluster versions; or add version gates.
  • All backports must be reviewed by the owning areas TL. For more information as to how that review should be conducted, please consult the backport
    policy
    .
If your backport adds new functionality, please ensure that the following additional criteria are satisfied:
  • There is a high priority need for the functionality that cannot wait until the next release and is difficult to address in another way.
  • The new functionality is additive-only and only runs for clusters which have specifically “opted in” to it (e.g. by a cluster setting).
  • New code is protected by a conditional check that is trivial to verify and ensures that it only runs for opt-in clusters. State changes must be further protected such that nodes running old binaries will not be negatively impacted by the new state (with a mixed version test added).
  • The PM and TL on the team that owns the changed code have signed off that the change obeys the above rules.
  • Your backport must be accompanied by a post to the appropriate Slack
    channel (#db-backports-point-releases or #db-backports-XX-X-release) for awareness and discussion.

Also, please add a brief release justification to the body of your PR to justify this
backport.

@blathers-crl blathers-crl bot added the backport Label PR's that are backports to older release branches label Oct 16, 2024
@cockroach-teamcity
Copy link
Member

This change is Reviewable

@asg0451 asg0451 requested a review from rharding6373 October 16, 2024 20:03
@asg0451 asg0451 merged commit 74be99f into cockroachdb:release-24.1 Oct 17, 2024
19 of 20 checks passed
@asg0451 asg0451 deleted the backport24.1-132761 branch October 17, 2024 13:27
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
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants