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

v1.3.7,Fatal: Could not open database: MemTableSize (4.0GB) must be < 4.0GB #2091

Closed
niocm opened this issue Dec 19, 2023 · 2 comments
Closed
Assignees

Comments

@niocm
Copy link

niocm commented Dec 19, 2023

System information

Geth
Version: 1.3.7
Git Commit: f28b98a
Git Commit Date: 20231219
Architecture: amd64
Go Version: go1.20.2
Operating System: linux

Expected behaviour

Running below command:
geth --config ./config.toml --datadir ./node --cache 51200 --rpc.allow-unprotected-txs --history.transactions=0 --syncmode=full --tries-verify-mode=local --pruneancient --db.engine=pebble --rpc.txfeecap 0 --rpc.gascap 0

Actual behaviour

root@Ubuntu-2204-jammy-amd64-base /jiedian/bsc # geth --config ./config.toml --datadir ./node  --cache 86016 --rpc.allow-unprotected-txs --history.transactions=0 --syncmode=full --tries-verify-mode=local --pruneancient --db.engine=pebble --rpc.txfeecap 0 --rpc.gascap 0
INFO [12-19|15:25:12.298] Starting Geth on BSC mainnet...
INFO [12-19|15:25:12.299] Maximum peer count                       ETH=200 LES=0 total=200
INFO [12-19|15:25:12.300] Smartcard socket not found, disabling    err="stat /run/pcscd/pcscd.comm: no such file or directory"
INFO [12-19|15:25:12.300] Using pebble as db engine
Fatal: Could not open database: MemTableSize (4.0GB) must be < 4.0GB

Steps to reproduce the behaviour

When submitting logs: please submit them as text and not screenshots.

@serfiraz21
Copy link

remove --cache flag or reduce to under 4gib

@flywukong
Copy link
Contributor

flywukong commented Dec 20, 2023

Please lower you cache setting -cache 51200 to run . The upstream pebble(cockroachdb/pebble#3008) exist an issue about it and we will have a temp fix on it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants