<p>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.... ).<br>
With logs from the seed node it should be possible to find the matching requests and disconnection.<br>
I agree we should handle such a close reason with starting a new request inside RequestDataManager on such disconnects.</p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/bisq-network/bisq/issues/3797?email_source=notifications&email_token=AJFFTNSZXLWBYTCLBBZ332DQZANXVA5CNFSM4J3NZF5KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHAVHJQ#issuecomment-566317990">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AJFFTNX5O4OHUDTKN4DJMTDQZANXVANCNFSM4J3NZF5A">unsubscribe</a>.<img src="https://github.com/notifications/beacon/AJFFTNXGEAA7K7WVQN4GPMDQZANXVA5CNFSM4J3NZF5KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHAVHJQ.gif" height="1" width="1" alt="" /></p>
<script type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/bisq-network/bisq/issues/3797?email_source=notifications\u0026email_token=AJFFTNSZXLWBYTCLBBZ332DQZANXVA5CNFSM4J3NZF5KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHAVHJQ#issuecomment-566317990",
"url": "https://github.com/bisq-network/bisq/issues/3797?email_source=notifications\u0026email_token=AJFFTNSZXLWBYTCLBBZ332DQZANXVA5CNFSM4J3NZF5KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHAVHJQ#issuecomment-566317990",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>