You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have multiple instances running on the same machine, with snapshots stored on another drive. Currently when I point them both to the snapshots folder (using docker-compose - /mnt/12TB/blockchain/snapshots:/blockchain/execution/snapshots).
When I point them at the same folder the second erigon node will fail with: openClient: mdbx_env_open: resource temporarily unavailable, label: downloader, trace: [kv_mdbx.go:262 downloader.go:471 downloader.go:90 backend.go:994 backend.go:298 node.go:115 main.go:70 make_app.go:42 command.go:274 app.go:332 app.go:309 main.go:38 proc.go:250 asm_amd64.s:1598]
Is there a way to share the snahshots folder?
The text was updated successfully, but these errors were encountered:
done: #8375
but still - I don't have any "receipt" on how 2 erigon instances can share snapshots folder. unless both of them using --snap.stop
External RPCDaemon can use same snapshots folder - because it subscribing to Erigon-events-stream about snapshots creation/deletion. But 2nd erigon node will not subscribe to this events-stream - unless - I implement this feature. Need to think about it.
I have multiple instances running on the same machine, with snapshots stored on another drive. Currently when I point them both to the snapshots folder (using docker-compose - /mnt/12TB/blockchain/snapshots:/blockchain/execution/snapshots).
When I point them at the same folder the second erigon node will fail with:
openClient: mdbx_env_open: resource temporarily unavailable, label: downloader, trace: [kv_mdbx.go:262 downloader.go:471 downloader.go:90 backend.go:994 backend.go:298 node.go:115 main.go:70 make_app.go:42 command.go:274 app.go:332 app.go:309 main.go:38 proc.go:250 asm_amd64.s:1598]
Is there a way to share the snahshots folder?
The text was updated successfully, but these errors were encountered: