[bisq-network/bisq] Startup problem on slow/degraded networks (the "3/4" problem) (#2547)

[Florian Reimair]

I had this very issue during vacation on a boat as well (= poor internet connection).

The issue most likely is that the initial data requests to the seednodes now exceed a size of 2MB and Bisq queries 2 seednodes simulaneously. If that amount of data cannot be transferred to the seed node before connection timeout, Bisq will never sync up.

I fear, that is not something we can easily fix. I thought about changing the syncing process to reduce the request size but that would require a massive change in the code base...

I will think about doing something to alert users on the issue if it happens (https://github.com/bisq-network/bisq/issues/2549) and maybe retry only a single seednode request - thus, reducing the payload by 50%.

Other than that, if you run into this issue, there is no quick way of fixing that.

-- 
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/2547#issuecomment-591967406
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20200227/22cf2a66/attachment.html>