[bisq-network/bisq] Seednode CLOSE_REQUESTED_BY_PEER + Timeout == 90s delay in startup (#3797)

[chimp1984]

The seednodes should not intentionally disconnect nodes. We should find out why that is the case (as you stated they are probably overloaded - or maybe its at the restart process.... ).
With logs from the seed node it should be possible to find the matching requests and disconnection.
I agree we should handle such a close reason with starting a new request inside RequestDataManager on such disconnects. 


-- 
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/3797#issuecomment-566317990
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20191216/f2610852/attachment.html>