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: go.mod: bump Pebble to 62fc20d22a8f #123314

Conversation

jbowens
Copy link
Collaborator

@jbowens jbowens commented Apr 30, 2024

Changes:

  • 62fc20d2 db,wal: avoid Batch.refData allocation
  • 55642e0c db: ensure Metrics.WAL.BytesWritten is nondecreasing
  • 7341c37a db: update flushableEntry.logSize during flushable ingest

Close #122915.
Informs #123236.
Release note: none.
Epic: none.
Release justification: bug fix for a performance regression and a bug fix for an observability bug.

Changes:

 * [`62fc20d2`](cockroachdb/pebble@62fc20d2) db,wal: avoid Batch.refData allocation
 * [`55642e0c`](cockroachdb/pebble@55642e0c) db: ensure Metrics.WAL.BytesWritten is nondecreasing
 * [`7341c37a`](cockroachdb/pebble@7341c37a) db: update flushableEntry.logSize during flushable ingest

Release note: none.
Epic: none.
@jbowens jbowens requested review from a team and sumeerbhola April 30, 2024 18:13
@jbowens jbowens requested a review from a team as a code owner April 30, 2024 18:13
Copy link

blathers-crl bot commented Apr 30, 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 and one additional
    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 Apr 30, 2024
@cockroach-teamcity
Copy link
Member

This change is Reviewable

@jbowens jbowens requested a review from dhartunian April 30, 2024 18:17
@jbowens
Copy link
Collaborator Author

jbowens commented Apr 30, 2024

TFTRs!

@jbowens jbowens merged commit 3e2cf04 into cockroachdb:release-24.1 Apr 30, 2024
19 of 20 checks passed
@jbowens jbowens deleted the jackson/pebble-release-24.1-62fc20d22a8f branch April 30, 2024 19:04
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.

None yet

4 participants