diff options
| -rw-r--r-- | src/rabbit_alarm.erl | 17 |
1 files changed, 1 insertions, 16 deletions
diff --git a/src/rabbit_alarm.erl b/src/rabbit_alarm.erl index bb2e386680..9a86d1c54d 100644 --- a/src/rabbit_alarm.erl +++ b/src/rabbit_alarm.erl @@ -94,9 +94,7 @@ register(Pid, HighMemMFA) -> %%---------------------------------------------------------------------------- init([]) -> - HWM = system_memory_high_watermark(), - {ok, #alarms{alertees = dict:new(), - system_memory_high_watermark = HWM}}. + {ok, #alarms{alertees = dict:new()}}. handle_call({register, Pid, HighMemMFA}, State = #alarms{alertees = Alertess}) -> @@ -138,19 +136,6 @@ code_change(_OldVsn, State, _Extra) -> %%---------------------------------------------------------------------------- -system_memory_high_watermark() -> - %% When we register our alarm_handler, the - %% system_memory_high_watermark alarm may already have gone - %% off. How do we find out about that? Calling - %% alarm_handler:get_alarms() would deadlock. So instead we ask - %% memsup. Unfortunately that doesn't expose a suitable API, so we - %% have to reach quite deeply into its internals. - {dictionary, D} = process_info(whereis(memsup), dictionary), - case lists:keysearch(system_memory_high_watermark, 1, D) of - {value, {_, set}} -> true; - _Other -> false - end. - alert(Alert, Alertees) -> dict:fold(fun (Pid, {M, F, A}, Acc) -> ok = erlang:apply(M, F, A ++ [Pid, Alert]), |