Create account

297d · BCHD
Reboot + reSync + full tx index + full address index
...wondering how long this would take on one of those legendary Arm nodes...
2019-09-12 06:07:58.980 [INF] BCHD: Version 0.14.7
replied 196d
Final Answer:
2019-12-22 07:32:03.307 [INF] SYNC: Processed 2 blocks in 32.3s (434 transactions, height 515639/614416 (83.92%), 2018-02-02 17:29:46 +0000 UTC, ~396 MiB cache)
replied 285d
2019-09-23 13:25:26.247 [INF] SYNC: Processed 1 block in 20.75s (479 transactions, height 390998/601495 (65.00%), 2015-12-30 16:58:09 +0000 UTC,...
replied 265d
2019-10-14 06:35:53.755 [INF] SYNC: Processed 1 block in 4m34.48s (2056 transactions, height 415334/604495 (68.71%), 2016-06-08 09:29:42 +0000 UTC)
replied 257d
2019-10-22 06:50:44.151 [INF] SYNC: Processed 1 block in 1m55.68s (2425 transactions, height 419621/605633 (69.29%), 2016-07-07 01:49:59 +0000 UTC,)
replied 232d
2019-11-16 05:50:32.285 [INF] SYNC: Processed 1 block in 34.41s (2143 transactions, height 458391/597755 (76.69%), 2017-03-22 11:28:58 +0000 UTC)
replied 257d
2019-10-22 07:26:14.226 [INF] CHAN: Flushing UTXO cache of ~237 MiB to disk. For large sizes, this can take up to several minutes...
2019-10-22 07:41:28.719 [INF] BCHD: Version 0.15.0
replied 257d
2019-10-22 07:43:10.879 [INF] CHAN: Reconstructing UTXO state after unclean shutdown. This may take a long time...
replied 256d
2019-10-22 15:40:19.178 [INF] SYNC: Processed 1 block in 4m13.35s (1778 transactions, height 419648/605704 (69.28%), 2016-07-07 06:10:27 +0000 UTC, ~285 MiB cache)
resumed....
replied 257d
2019-10-22 07:43:10.831 [INF] CHAN: Block ~30819bceba406cf3fa50a51d3091ffa7766a0563db1948e (height=419647) ancestor of chain tip not marked as valid, upgrading to valid for consistency
replied 293d
with a SSD or HDD?
replied 293d
HDD in a wimpy VPS.
2019-09-15 16:34:45.566 [INF] SYNC: Processed 1 block in 12.83s (2504 transactions, height 348882/600373 (58.11%), 2015-03-23 19:38:48 +0000 UTC, ~375 MiB cache)
replied 293d
replied 293d
Glaciers melt faster than node SYNCing
replied 293d
This is will all indexers, gRPC, etc. All the extra features.
replied 293d
With* Fuck
replied 297d
In my experience, the address index makes full sync significantly longer and takes up about 50 GB of extra data. I wouldn't recommend enabling it unless you actually need it.
replied 296d
It is a requirement if you want to run bchd with GRPC
replied 296d
Good to know, thanks!
replied 297d
point noted,
but I thought I would need that to use the bchwallet (- for which exactly -zero- instructions exist on how to use it)
replied 297d
I don't think you need it for bchwallet. It's only used by the searchrawtransactions RPC AFAIK which lets you query any address (as opposed to solely the addresses in your wallet).
replied 297d
I thought the tx index was for searchrawtransactions
and that the address index was for wallet, - oh well...
replied 297d
You can always drop it with https://github.com/gcash/bchd/blob/3ef1172ecbabb4131c5bb45dbcd9a6a714ee7d49/config.go#L179 if it hogs too much resources.