Both server node and thin client are on the same computer, each running in a separate Docker container with network „host“. CPU load does not seem to be an issue and other server nodes on the same computer and from other computers connect to the cluster just fine without such connection issues. I‘ll check the server logs more thoroughly. On 15.06.22 at 21:14, Pavel Tupitsyn wrote:
From: "Pavel Tupitsyn" <ptupit...@apache.org>
Date: 15. June 2022 To: "user" <user@ignite.apache.org> Cc: Subject: Re: ThinClient connection refused / disconnect Idle timeout is disabled by default.
Regarding connection issues, either the server is overloaded and can't accept connections, or there are network issues.
1. Check if the network between client and server is reliable enough (measure speed, check packet loss)
2. Check server logs and resource utilization
On Wed, Jun 15, 2022 at 5:47 PM <don.tequ...@gmx.de> wrote:
Hi, |
- ThinClient connection refused / disconnect don . tequila
- Re: ThinClient connection refused / disconnect Pavel Tupitsyn
- Re: Re: ThinClient connection refused / disconnect don . tequila
- Re: ThinClient connection refused / disconnect don . tequila
- Re: ThinClient connection refused / discon... Pavel Tupitsyn