docs: document erigondb domain merge cap flag [main]#21130
Conversation
|
Lines to restore in |
yperbasis
left a comment
There was a problem hiding this comment.
TL;DR: One factual error to fix before merge — the rest of the diff is correct. The PR was regenerated from a v3.4.1 binary on release/3.4, so it drops a flag (--erigondb.domain.steps-in-frozen-file) that exists on main's target binary.
Verification against current main
| Claim in PR | Source | Status |
|---|---|---|
--rpc.subscription.filters.maxlogs default → 10000 |
rpc/rpchelper/config.go:35 |
✅ correct |
--rpc.subscription.filters.maxheaders default → 10000 |
rpc/rpchelper/config.go:36 |
✅ correct |
--rpc.subscription.filters.maxtxs default → 10000 |
rpc/rpchelper/config.go:37 |
✅ correct |
--log.dir.verbosity default → dbug |
node/logging/flags.go:69 + common/log/v3/logger.go:36 |
✅ correct |
--caplin.nat exists, accepted values |
cmd/utils/flags.go:880 + p2p/nat/nat.go:69 |
✅ correct |
--caplin.columns-keep-slots default 131072 (~18 days) |
cmd/utils/flags.go:1030-1034 |
✅ correct |
--erigondb.domain.steps-in-frozen-file removed as stale |
cmd/utils/flags.go:1149 + node/cli/default_flags.go:268 |
❌ wrong on main |
Critical issue — erigondb.domain.steps-in-frozen-file is not stale on main
The PR description says the flag was "removed in v3.4 source." That's apparently true on release/3.4 — the v3.4.1 commit 6fdfdb7b has no ErigondbDomainStepsInFrozenFile symbol. But this PR targets main, where:
cmd/utils/flags.go:1149defines the flag.node/cli/default_flags.go:268registers it on the main erigon binary.- PR #21025 (merged 2026-05-07, five days before this PR) actively extended the flag into
integration stage_execanderigon seg retire. - PR #20730 originally added its documentation block — which this PR now reverses.
The regenerated #Options block was produced from a v3.4.1 binary, so it understandably doesn't list the flag. The result is documentation on main that contradicts main's source.
Options to fix:
- Preferred: regenerate the
#Optionsblock from amain-built erigon binary so all of main's flags are documented, and restore theerigondb.domain.steps-in-frozen-fileentry. The bot should source its dump fromHEAD, not the latest tag. - Acknowledge in the PR title/description that this gitbook docs update on
mainintentionally mirrorsv3.4.1(since gitbook is slated for removal in #21013) and the flag-set divergence is accepted. I'd recommend against this — gitbook is still the published docs formainuntil #21013 lands.
Smaller observations
caplin.nataccepted-values list: the PR enumerates\"\",extip:1.2.3.4,stun,stun:<host>,upnp,pmp,pmp:192.168.0.1. The upstreamp2p/nat.Parsealso accepts the aliasesnone/off/any/auto/on/natpmp/nat-pmp. The source-level Usage string atcmd/utils/flags.go:880doesn't list them either, so this is consistent — but worth a thought for completeness.- Overlap with
--caplin.enable-upnp: the doc still lists both--caplin.enable-upnp(bool) and--caplin.nat(which itself acceptsupnp/pmp). Setting both is confusing; not introduced by this PR, but a one-line note in thecaplin.natblurb pointing users at the preferred form would help. - r3.4 PR includes a
nat.mdsmart-quote fix that this PR doesn't carry. Probably because gitbook doesn't have the equivalent file, so this is fine. - Style: the new
caplin.natentry is one dense sentence followed by inline backticks. A short bullet list of accepted values (matching the gitbook style of the other long blurbs in this file) would render more clearly. Not a blocker.
Risks
- If merged as-is, operators reading docs.erigon.tech (which serves gitbook from
main) won't see the--erigondb.domain.steps-in-frozen-fileoverride knob even though main's binary supports it. That's a performance-tuning flag with a "use with care" advisory — losing it from the docs is a real regression for ops.
Recommendation
Don't merge until the #Options block is regenerated from a main-built erigon binary (so the live flag set on main is documented). The rest of the inline edits are correct and can stand once the dump is refreshed.
|
Addressed the blocking review point in 5d7164b:
Local check: |
# Conflicts: # docs/gitbook/src/fundamentals/configuring-erigon/README.md
|
Resolved the current Resolution details:
Local check: |
There was a problem hiding this comment.
Pull request overview
Updates the Docusaurus CLI reference to document the --erigondb.domain.steps-in-frozen-file flag, which overrides the steps_in_frozen_file value from erigondb.toml specifically for the domain merge cap (leaving history and inverted-index merges unchanged).
Changes:
- Adds documentation for
--erigondb.domain.steps-in-frozen-file, including semantics and default behavior. - Notes safe-usage guidance and that the default is unset (falls back to
erigondb.toml).
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Summary
Current
mainhas migrated away from GitBook to Docusaurus. This PR now resolves the previous GitBook conflict by accepting the GitBook removal frommainand carrying the surviving docs fix into the current Docusaurus page.Change
--erigondb.domain.steps-in-frozen-filetodocs/site/docs/fundamentals/configuring-erigon/index.mdx.Source-of-truth check
This PR targets
main, so the flag was verified againstorigin/main:cmd/utils/flags.godefinesErigondbDomainStepsInFrozenFileFlagwith nameerigondb.domain.steps-in-frozen-file.node/cli/default_flags.goregisters it for the mainerigonbinary.Conflict resolution
docs/gitbook/src/fundamentals/configuring-erigon/README.mdwas deleted on currentmain; the PR accepts that deletion and does not reintroduce GitBook.main.Local checks
git diff --check origin/main...HEADpasses.npm --prefix docs/site run typecheckcould not run locally becausedocs/sitedependencies are not installed in this worktree (tscmissing); CI should run the docs-site checks.🤖 Generated by weekly docs maintenance routine