miguel.g.gar...@ericsson.com
Subject: Re: Requests taking too long if one member of the cluster fails
Yes, lowering the member timeout is one approach I’ve seen taken for
applications that demand ultra low latency. These workloads need to provide
not just low “average” or even p99 latency, but put
Yes, lowering the member timeout is one approach I’ve seen taken for
applications that demand ultra low latency. These workloads need to provide
not just low “average” or even p99 latency, but put a hard limit on the max
value.
When you do this you need to ensure coherency across at all
ario
From: John Blum mailto:jb...@vmware.com>>
Sent: Saturday, November 21, 2020 9:41 PM
To: dev@geode.apache.org<mailto:dev@geode.apache.org>
mailto:dev@geode.apache.org>>
Cc: miguel.g.gar...@ericsson.com<mailto:miguel.g.gar...@ericsson.com>
mailto:mig
ber 23, 2020 3:42 AM
To: dev@geode.apache.org
Cc: miguel.g.gar...@ericsson.com
Subject: Re: Requests taking too long if one member of the cluster fails
Hi Mario-
1) Regarding why only write to the primary (bucket) of a PR (?)... again, it
has to do with consistency.
Fundamentally, a distributed
rres
Sent: Saturday, November 21, 2020 1:40 PM
To: dev@geode.apache.org
Cc: miguel.g.gar...@ericsson.com
Subject: Re: Requests taking too long if one member of the cluster fails
Thanks @John Blum<mailto:jb...@vmware.com> for your detailed explanation! It
helped me to better understand how
o/G7n6T0M/Geode-Server-Kill.jpg
Thanks again.
BR,
Mario
From: John Blum
Sent: Saturday, November 21, 2020 9:41 PM
To: dev@geode.apache.org
Cc: miguel.g.gar...@ericsson.com
Subject: Re: Requests taking too long if one member of the cluster fails
DISCLAIMER:
Cc: miguel.g.gar...@ericsson.com
Subject: Requests taking too long if one member of the cluster fails
Hi,
I've been looking into the following issue:
"Whenever performing a stress test on a Geode cluster and forcefully killing
one of the members, all the threads in the application get stuc
Hi,
I've been looking into the following issue:
"Whenever performing a stress test on a Geode cluster and forcefully killing
one of the members, all the threads in the application get stuck".
To give more context these are the conditions under the test is performed:
* A cluster is deployed
