chore: upgrade databend-meta stack to land rotbl 0.2.10#19703
Merged
drmingdrmer merged 1 commit intodatabendlabs:mainfrom Apr 12, 2026
Merged
chore: upgrade databend-meta stack to land rotbl 0.2.10#19703drmingdrmer merged 1 commit intodatabendlabs:mainfrom
drmingdrmer merged 1 commit intodatabendlabs:mainfrom
Conversation
xp-trumpet
approved these changes
Apr 11, 2026
Collaborator
xp-trumpet
left a comment
There was a problem hiding this comment.
@xp-trumpet reviewed 3 files and all commit messages.
Reviewable status:complete! all files reviewed, all discussions resolved (waiting on drmingdrmer).
Contributor
🤖 CI Job Analysis
📊 Summary
❌ NO RETRY NEEDEDAll failures appear to be code/test issues requiring manual fixes. 🔍 Job Details
🤖 AboutAutomated analysis using job annotations to distinguish infrastructure issues (auto-retried) from code/test issues (manual fixes needed). |
Bump `databend-meta` to `260312.6.0`, `databend-meta-client` to `260205.5.0`, and `databend-base` to `0.3.0`. The three move in lockstep because both the server and client trees consume `rotbl 0.2.10`, which eliminates `Mutex<File>` serialization in the block reader (pread-based `ReaderAt`) and switches the block cache from a hand-rolled LRU to `moka::sync::Cache` with singleflight loading — ~78-95x throughput improvement under contention. `databend-base 0.3.0` is part of the same cascade: the new `databend-meta` server pins `databend-base ^0.3.0` because the `histogram` module was extracted into the standalone `base2histogram` crate. `databend-meta-client 260205.5.0` is the corresponding release of the r-260205 client line carrying the same `databend-base` floor, so the two trees coexist under a single `[patch.crates-io]` entry. Drop `snapshot_db_block_cache_item` from `RaftConfig`: rotbl 0.2.10's `moka::sync::Cache` cannot enforce an item count and a byte weight independently, so byte capacity is now the single sizing knob. `--snapshot-db-block-cache-size` remains and still defaults to 1 GiB.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I hereby agree to the terms of the CLA available at: https://docs.databend.com/dev/policies/cla/
Summary
chore: upgrade databend-meta stack to land rotbl 0.2.10
Bump
databend-metato260312.6.0,databend-meta-clientto260205.5.0, anddatabend-baseto0.3.0. The three move inlockstep because both the server and client trees consume
rotbl 0.2.10, which eliminatesMutex<File>serialization in theblock reader (pread-based
ReaderAt) and switches the block cachefrom a hand-rolled LRU to
moka::sync::Cachewith singleflightloading — ~78-95x throughput improvement under contention.
databend-base 0.3.0is part of the same cascade: the newdatabend-metaserver pinsdatabend-base ^0.3.0because thehistogrammodule was extracted into the standalonebase2histogramcrate.
databend-meta-client 260205.5.0is the corresponding releaseof the r-260205 client line carrying the same
databend-basefloor,so the two trees coexist under a single
[patch.crates-io]entry.Drop
snapshot_db_block_cache_itemfromRaftConfig: rotbl 0.2.10'smoka::sync::Cachecannot enforce an item count and a byte weightindependently, so byte capacity is now the single sizing knob.
--snapshot-db-block-cache-sizeremains and still defaults to 1 GiB.Tests
Type of change
Related Issues
This change is