diff options
| author | Matthias Radestock <matthias@lshift.net> | 2008-10-05 11:44:50 +0100 |
|---|---|---|
| committer | Matthias Radestock <matthias@lshift.net> | 2008-10-05 11:44:50 +0100 |
| commit | 6bc2454ddc1c7b576b950e62cd0876738f157b38 (patch) | |
| tree | 261f8247056b826cd2fd6a4d5d8b779bee798258 | |
| parent | 6c1976f5b38781bb8a8c297cc438dcee96035910 (diff) | |
| download | rabbitmq-server-6bc2454ddc1c7b576b950e62cd0876738f157b38.tar.gz | |
document limitation of initial effectiveness of memsup checks
| -rw-r--r-- | src/rabbit_alarm.erl | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/src/rabbit_alarm.erl b/src/rabbit_alarm.erl index f38651d1..d5cbf066 100644 --- a/src/rabbit_alarm.erl +++ b/src/rabbit_alarm.erl @@ -56,6 +56,11 @@ start() -> %% a granularity of minutes. So we have to peel off one layer of %% the API to get to the underlying layer which operates at the %% granularity of milliseconds. + %% + %% Note that the new setting will only take effect after the first + %% check has completed, i.e. after one minute. So if rabbit eats + %% all the memory within the first minute after startup then we + %% are out of luck. ok = os_mon:call(memsup, {set_check_interval, ?MEMSUP_CHECK_INTERVAL}, infinity), |