Error NO_NODE_FOUND_TO_DOWNLOAD_CHUNK

This error often occurs on ĞTest network and less frequently on Ğ1, still it avoids the synchronization process to finish.

changed the description

Also, it seems that the download speed rate is lower on Duniter 1.7 than 1.6.

Bug found: on the initialization of the sync, a set of few nodes (approx 3-4) is selected and then Duniter always sync on these, ignoring any other node.

Also, on a given set, while a node isn't refusing connection Duniter keeps downloading mostly on it. This mostly leads to a ban from the remote node. And then Duniter (possibly) keeps going with the same behavior on another node of the set, until it gets definitely ban by all the downloading set.

Normally, Duniter tries to load-balance the downloading of the blocks which helps it not getting banned at all.

mentioned in commit eaf88870

mentioned in commit 65ebf762

mentioned in commit 25592ec7

mentioned in commit 43fa0c25

closed