diff options
| author | Francesco Mazzoli <francesco@rabbitmq.com> | 2012-07-11 13:16:22 +0100 |
|---|---|---|
| committer | Francesco Mazzoli <francesco@rabbitmq.com> | 2012-07-11 13:16:22 +0100 |
| commit | 5637ca640ae519af24b6f92c8a3a08569320e186 (patch) | |
| tree | 3a69bf8cf4e38141cc5fb0ac933dfe4c8a17679f /src/rabbit_disk_monitor.erl | |
| parent | ee9f396a11946ea2d47f4e6326eefca4c86d774c (diff) | |
| download | rabbitmq-server-5637ca640ae519af24b6f92c8a3a08569320e186.tar.gz | |
let `rabbit_alarm' handle everything in place of `alarm_handler'
No logging on set/clear alarm yet, me and Simon agree that we should do
logging only on the events that rabbit knows it should be receiving
(right now the resource limits ones)
Diffstat (limited to 'src/rabbit_disk_monitor.erl')
| -rw-r--r-- | src/rabbit_disk_monitor.erl | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/src/rabbit_disk_monitor.erl b/src/rabbit_disk_monitor.erl index 58375abb..e72181c0 100644 --- a/src/rabbit_disk_monitor.erl +++ b/src/rabbit_disk_monitor.erl @@ -149,10 +149,10 @@ internal_update(State = #state { limit = Limit, case {Alarmed, NewAlarmed} of {false, true} -> emit_update_info("exceeded", CurrentFreeBytes, LimitBytes), - alarm_handler:set_alarm({{resource_limit, disk, node()}, []}); + rabbit_alarm:set_alarm({{resource_limit, disk, node()}, []}); {true, false} -> emit_update_info("below limit", CurrentFreeBytes, LimitBytes), - alarm_handler:clear_alarm({resource_limit, disk, node()}); + rabbit_alarm:clear_alarm({resource_limit, disk, node()}); _ -> ok end, |