Re: Geode self-protection about overload

Hi again, I finally figured out why I was not getting the "ServerConnectivityException" when executing a big amount of functions in Geode while I did get the exception when running lots of gets/puts/queries. The reason is that the ConnectionImpl::execute(Op op) does not use the timeout set by

Re: Geode self-protection about overload

Hi Anthony, Thanks again for the information. I have played a bit with the the client timeouts and retries and have seen operations being rejected when load is high due to get or put operations. Nevertheless, I have not seen that happen when the load in the server is high due to functions invo

Re: Geode self-protection about overload

The primary load limiter between the client tier and the Geode servers is via the max connections limit as noted in this writeup: https://cwiki.apache.org/confluence/display/GEODE/Resource+Management+in+Geode When

Re: Geode self-protection about overload

Hi Anthony! Thanks a lot for your prompt answer. I think it is great that Geode can preserve the availability and predictable low latency of the cluster when some members are unresponsive by means of the GMS. My question was more targeted to situations in which the load received by the cluste

Re: Geode self-protection about overload

Hi Alberto! Great questions. One of the fundamental characteristics of Geode is its Group Membership System (GMS). You can read more about it here [1]. The membership system ensures that failures due to unresponsive members and/or network partitions are detected quickly. Given that we use s