Parity taking days to (fail to) sync on warp-barrier #8531
Description
I'm running:
- Which Parity version?:
v1.10.2-beta-f4ae813-20180423/x86_64-linux-gnu/rustc1.25.0
- Which operating system?:
Ubuntu 16.06
(recently installed)- How installed?:
sudo bash <(curl https://get.parity.io -kL)
- Are you fully synchronized?: no
- Which network are you connected to?: ethereum (default)
- Did you try to restart the node?: yes
Parity taking days to (fail to) sync despite multiple restarts as follows:
-
Initial run started with canonical
parity
- cancelled after a couple of days, deleted~/.local/share/io.parity.ethereum
-
parity --mode active --tracing off --pruning fast --db-compaction ssd --cache-size 1024
- again cancelled, deleted parity dir and then: -
parity --db-compaction ssd --cache-size 1024 --warp-barrier 5520000
This last execution was left running for 48 hours and the last line of the log at that point:
2018-05-02 15:52:13 Syncing #4179651 a017…7492 5 blk/s 434 tx/s 28 Mgas/s 0+ 453 Qed #4180107 25/25 peers 66 MiB chain 393 MiB db 43 MiB queue 13 MiB sync RPC: 0 conn, 0 req/s, 44057 µs
My system specs are as follows:
CPU: Intel i7 6700K
GPU: GeForce GTX 1060 6GB
RAM: 16GB DDR4 SDRAM
HD: 128GB M.2 SSD
Internet: 950 Mb/s down, 120 Mb/s up, fiber
Clock is synced. 8GB swapfile is 152M used.
StackExchange discussion here, https://ethereum.stackexchange.com/questions/46950/parity-sync-time-april-2018-many-days-normal
Raising a bug as requested by Tbaut. I would be happy to help with diagnosis and testing.
Thank you,
Darren