Alex Sharov
Alex Sharov
``` ./build/bin/mdbx_chk -vvv /data2/poly-archive/erigon_data ``` if it will return same error, can try: ``` git pull git checkout e35_mdbx_v0_13 make db-tools ./build/bin/mdbx_chk -vvv /data2/poly-archive/erigon_data ``` if this command doesn't return...
please rise question in #polygon channel on Erigon's discord server https://github.com/erigontech/erigon?tab=readme-ov-file#erigon-discord-server - or at some Polygon support channel. we don't control polygon's snapshot files.
agree. created `beta` milestone. moved issue there.
I know what it means - just it feels redundant (not sure if it adds more clarity for user or adds more mess): `downloading=100Kb/s hashing=20kb/s` vs `rate=120Kb/s downloading=100Kb/s hashing=20kb/s` `downloading=0Kb/s...
as you can see it's confusing: https://github.com/erigontech/erigon/issues/13250
Reduce —db.reqd.concurrency
This limit is for main db only (it handling most of RPC requests, etc...). But we also have many databases - they are unlimited but must not produce much threads....
you can add `--pprof` and show: ``` curl -s -v http://localhost:6060/debug/pprof/goroutine?debug=1 > goroutine.txt go tool pprof -png http://127.0.0.1:6060/debug/pprof/profile/?seconds\=20 > cpu.png go tool pprof -alloc_objects -png http://127.0.0.1:6060/debug/pprof/heap?seconds\=20 > mem.png ```
do `rm -rf datadir/nodes` `rm -rf datadir/txpool` here is the fix: https://github.com/erigontech/erigon/pull/13218
tnx for reminding. team will take a look