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 stuck". To give more context these are the conditions under the test is performed: * A cluster is deployed

Re: Requests taking too long if one member of the cluster fails

DISCLAIMER: I am not knowledgeable about the Native Client (implementation) nor am I commenting specifically on the perf you are seeing, which can have many factors. However, in general... Given you are performing "put" operations on a PR, then for consistency reasons, Geode is always going to

Re: Requests taking too long if one member of the cluster fails

Thanks @John Blum for your detailed explanation! It helped me to better understand how redundancy works. Thing is that all our use cases requires a really low response time when performing operations. Under normal conditions a "put" takes a few milliseconds, but in the c