-
Notifications
You must be signed in to change notification settings - Fork 232
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
Disallow --rocksdb-shred-compaction fifo in the validator #3451
Conversation
The use of fifo compaction in rocksdb is deprecated (as of v2.0). The current behavior emits a warning if fifo is set. This change removes "fifo" as an option, leaving "level" as the only valid value for --rocksdb-shred-compaction
Backports to the beta branch are to be avoided unless absolutely necessary for fixing bugs, security issues, and perf regressions. Changes intended for backport should be structured such that a minimum effective diff can be committed separately from any refactoring, plumbing, cleanup, etc that are not strictly necessary to achieve the goal. Any of the latter should go only into master and ride the normal stabilization schedule. Exceptions include CI/metrics changes, CLI improvements and documentation updates on a case by case basis. |
The use of fifo compaction in rocksdb is deprecated (as of v2.0). The current behavior emits a warning if fifo is set. This change removes "fifo" as an option, leaving "level" as the only valid value for --rocksdb-shred-compaction (cherry picked from commit fddc554)
…port of #3451) (#3464) Disallow --rocksdb-shred-compaction fifo in the validator (#3451) The use of fifo compaction in rocksdb is deprecated (as of v2.0). The current behavior emits a warning if fifo is set. This change removes "fifo" as an option, leaving "level" as the only valid value for --rocksdb-shred-compaction (cherry picked from commit fddc554) Co-authored-by: steviez <steven@anza.xyz>
Problem
Fifo compaction in rocksdb (Blockstore) was deprecated in v2.0 (see #1882). Currently, a warning is emitted but use of
fifo
is still permitted.Summary of Changes
This change actually makes
fifo
an invalid option for--rocksdb-shred-compaction
, leavinglevel
as the only valid option.The actual fifo code that is plumbed down several layers will be removed in a subsequent PR
Testing
Started a validator real quick and ensured that things errored out with
--rocksdb-shred-compaction fifo
and that--rocksdb-shred-compaction level
OR not specifying that flag at all proceeded without issue