Roman Zeyde
Roman Zeyde
We indeed shouldn't exit electrs if mempool sync fails: https://github.com/romanz/electrs/commit/23c775fb4702ad90428522478f2af1e7aed64111
Could you please try to reproduce this issue on the latest `v0.9.0` release?
Seems to be reproduced when syncing testnet: ``` [2021-10-03T12:25:37.879Z INFO electrs::metrics::metrics_impl] serving Prometheus metrics on 127.0.0.1:14224 [2021-10-03T12:25:39.336Z INFO electrs::db] "./db/testnet": 20 SST files, 2.414105025 GB, 0.242684629 Grows [2021-10-03T12:25:39.336Z DEBUG electrs::db]...
It seems that bitcoind RPC is not available during IBD - and `getblockchaininfo` times out (while waiting for the sync to finish): https://github.com/romanz/electrs/blob/2bc61b73d0942e21573a5257e2d5589f8e3d65c7/src/daemon.rs#L26
For now, it should be OK to restart electrs after such error.
I don't use docker for running electrs personally - but PRs are welcome :)
Sorry for the delayed response... please take a look at: https://github.com/lukechilds/electrs-next/blob/master/docker-compose.yml cc: @lukechilds
@schildbach Could you please try latest `v0.9.0` release?
Good idea! I'd start with adding support for pruned nodes - it would allow running Electrum with much less storage required.
Actually, we can support this now since each index row also contain the relevant block height: https://github.com/romanz/electrs/blob/master/doc/schema.md Maybe it is possible to use https://github.com/facebook/rocksdb/wiki/Compaction-Filter?