geode-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alberto Gomez <>
Subject Geode self-protection about overload
Date Fri, 10 May 2019 10:22:36 GMT
Hi Geode community!

I'd like to know if Geode implements any kind of self-protection against overload. What I
mean by this is some mechanism that allows Geode servers (and possibly locators) to reject
incoming operations before processing them when it detects that it is not able to handle the
amount of operations received in a reasonable way (with reasonable latency and without experiencing
processes crashing).

The goal would be to make sure that Geode (or some parts of it) do not crash under too heavy
load and also that the latency level is always under control at least for the amount of traffic
the Geode cluster is supposed to support.

If Geode does not offer such mechanism, I would also like to get your opinion about this possible
feature, (if you find it interesting) and also on how it could be implemented. One possible
approach could be having some measure of the current CPU consumption that allows to decide
if a given operation must be processed or not, taking into account the CPU consumption value
with respect to an overload threshold.

Thanks in advance for your answers,

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message