: Wednesday, February 24, 2021 7:38 AM
To: dev@geode.apache.org
Subject: Re: Question about closing of all connections towards an endpoint in
C++ native client
Oh good! 1.14 is on its way, so problem solved! ;)
> On Feb 24, 2021, at 7:31 AM, Alberto Gomez wrote:
>
> Thanks Jake. I tota
what I said in my previous e-mail
> pertained to the C++ client 1.13 version and older.
>
> Alberto
>
> From: Jacob Barrett
> Sent: Wednesday, February 24, 2021 4:24 PM
> To: dev@geode.apache.org
> Subject: Re: Question about closing of a
: Jacob Barrett
Sent: Wednesday, February 24, 2021 4:24 PM
To: dev@geode.apache.org
Subject: Re: Question about closing of all connections towards an endpoint in
C++ native client
The Java client does the same thing under certain conditions. Neither of the
clients should do this though. I think
The Java client does the same thing under certain conditions. Neither of the
clients should do this though. I think this model is way too overaggressive. I
think we should remove that logic entirely. If we think we want something that
proactively checks the other connections to that server we co
Hi,
Running some tests with the C++ native client and looking at the code, I have
observed that when an error in a connection towards an endpoint (timeout, IO
error) is detected, not only the faulty connection is closed but the endpoint
is set to "not connected" status which eventually provokes
