[bisq-network/bisq] Improve BSQ block requests (#3094)

[jmacxx]

Experienced this today in support.  User reported their DAO rebuild stopped syncing without any feedback.  Upon restarting Bisq the resync would start but eventually stall again.  Logs revealed that it was downloading blocks from a seednode, then after some time it would get disconnected and a connection would be made to a new seednode.  After 3 such disconnects it would simply give up with the log message "We tried 4 times but could not connect to a seednode".

https://github.com/bisq-network/bisq/blob/d0e88f7e2a63ca4dfd75c757c79deaa5be5c845e/core/src/main/java/bisq/core/dao/node/lite/network/LiteNodeNetworkService.java#L354-L358

I propose removing the MAX_RETRY limit and change the retry backoff time to `(retryCounter * RETRY_DELAY_SEC)` so that the subsequent seednode connection attempts get further and further apart, much like how login screens increase the time before you can make another attempt at entering your password.


-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/bisq-network/bisq/issues/3094#issuecomment-945322947
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20211017/f02bc7b2/attachment-0001.htm>