fix: fix pebble mem table size boundary error#2120
Merged
zzzckck merged 1 commit intobnb-chain:developfrom Jan 3, 2024
Merged
Conversation
jingjunLi
approved these changes
Dec 28, 2023
This was referenced Jan 22, 2024
Merged
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
5 participants
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.
Description
If mem table size exceeds 4G, the memtable will be set to 4G in bsc code . But Pebble has not handled this boundary well , it require less than 4G but not equal 4G . (cockroachdb/pebble#3008)
Rationale
solve issue(#2091)
Example
add an example CLI or API response...
Changes
Notable changes: