summaryrefslogtreecommitdiff
path: root/src/rabbit_alarm.erl
Commit message (Collapse)AuthorAgeFilesLines
* Delayed restart of the disk monitor.Simon MacMullen2014-04-091-1/+2
|
* Update copyright for 2014bug25940Simon MacMullen2014-03-171-1/+1
|
* Merge bug25191Simon MacMullen2013-08-061-36/+36
|\
| * Convert Event set / clear to Alert true / false since that's how it is ↵bug25191Simon MacMullen2013-07-301-17/+8
| | | | | | | | everywhere else. Further simplify. Remove a no longer true comment.
| * Inlining and cosmetic.Simon MacMullen2013-07-301-19/+11
| |
| * UntabifySimon MacMullen2013-07-301-21/+21
| |
| * Deliver all alart notification to handle overlapping alarmsMichael Klishin2013-06-241-22/+12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | connection.blocked requires us to track resources we are conserving. This means the old logic of determining edge state transitions for alarms does not work any more. Instead of using the old strategy of comparing alarmed node collection sizes, instead of pass around what event the notification is for and simply deliver it to the relevant nodes. This requires that rabbit_alarm event consumers handle duplicate notifications. They already do so after earlier changes on branch bug25191. This makes connection unblocking work correctly in the following sequence of events: * memory alarm set for node A * disk alarm set for node A * memory alarm cleared for node A * disk alarm cleared for node A as well as other similar scenarios with overlapping alarms. This slighly increases internode and intranode message traffic of alarm notifications. Since alarms occur rarely in well-monitored systems, this is a reasonable trade-off.
| * Use lists:keymember hereMichael Klishin2013-06-211-1/+1
| |
| * Correctly determine duplicate alarms when alarm is clearedMichael Klishin2013-06-211-20/+23
| | | | | | | | | | Also, don't bother doing anything on duplicate alarms, per review feedback.
| * Don't log duplicate alarm warningsMichael Klishin2013-06-201-8/+19
| |
| * Make sure the list of alarm resources is uniqueMichael Klishin2013-06-201-1/+8
| |
| * Make sure set_alarm is idempotentMichael Klishin2013-06-191-1/+2
| | | | | | | | By making sure alarms list is unique.
| * Don't crash when an alarm is cleared when there's nothing to clearMichael Klishin2013-06-191-1/+6
| |
| * Merge defaultSimon MacMullen2013-04-161-3/+3
| |\
| | * merge default into bug25191Matthias Radestock2013-01-101-11/+9
| | |\ | | | | | | | | | | | | and some tiny refactoring
| | * | send connection.{blocked,unblocked}Matthias Radestock2013-01-101-3/+4
| | | |
* | | | s/VMware/GoPivotal/gSimon MacMullen2013-07-011-2/+2
|/ / /
* | | stable to defaultSimon MacMullen2013-03-191-3/+11
|\ \ \
| * | | These log messages do not necessarily make their implications clear enough; ↵Simon MacMullen2013-03-191-3/+11
| | | | | | | | | | | | | | | | I can imagine people's eyes glazing over them. Try to deal with that.
* | | | stable to defaultSimon MacMullen2013-01-241-1/+1
|\ \ \ \ | |/ / / | | | / | |_|/ |/| |
| * | Update copyright 2013bug25343Emile Joubert2013-01-231-1/+1
| |/
* | cosmetic renameMatthias Radestock2013-01-101-9/+8
|/
* cast not call.Simon MacMullen2012-11-121-3/+2
|
* Use background_gc when the memory alarm goes off.Simon MacMullen2012-11-121-1/+1
|
* inlineMatthias Radestock2012-11-071-3/+5
|
* propagate resultbug25277Matthias Radestock2012-11-061-1/+1
|
* send out the alarm event before gcMatthias Radestock2012-11-061-2/+2
| | | | so subscribers can react to it quickly
* cosmeticMatthias Radestock2012-11-061-4/+3
|
* SimplifySimon MacMullen2012-11-061-8/+9
|
* GC the world when memory alarm goes off.Simon MacMullen2012-11-061-4/+7
|
* resource_limit alarms are always atoms, and we don't need quotes around themSimon MacMullen2012-07-181-2/+2
|
* All our log invocations should end in ~nSimon MacMullen2012-07-181-6/+6
|
* do not blowup on unrecognised alarmsFrancesco Mazzoli2012-07-131-0/+6
|
* aligning things, part twoFrancesco Mazzoli2012-07-131-3/+2
|
* because we all love aligned arrows (especially Matthias)Francesco Mazzoli2012-07-131-2/+1
|
* cosmeticsFrancesco Mazzoli2012-07-131-8/+4
|
* add a `get_alarms/0' to `rabbit_alarm', equivalent to ↵Francesco Mazzoli2012-07-131-19/+31
| | | | `alarm_handler:get_alarms/0'
* `rabbit_alarm' on its own again, added callbacks to fhc and `vm_memory_monitor'Francesco Mazzoli2012-07-131-14/+29
|
* do not take place of `alarm_handler', just pretty print what we're interested inFrancesco Mazzoli2012-07-121-24/+21
|
* log the resource limit alarmsFrancesco Mazzoli2012-07-111-2/+4
|
* let `rabbit_alarm' handle everything in place of `alarm_handler'Francesco Mazzoli2012-07-111-13/+26
| | | | | | 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)
* Allow nodes to start up in alerted statebug24961Emile Joubert2012-05-241-6/+6
|
* We don't need this any more, just inform the registree once.Simon MacMullen2012-03-291-2/+2
|
* AHEMSimon MacMullen2012-03-291-1/+1
|
* Revert odd changeSimon MacMullen2012-03-291-1/+1
|
* Separate alarm from disk monitor and disk free status reportingEmile Joubert2012-03-281-9/+0
|
* Alert remote and local alarm subscribers differentlyEmile Joubert2012-03-281-8/+10
|
* Wrap long linesEmile Joubert2012-03-261-7/+10
|
* Merge headsEmile Joubert2012-03-261-6/+8
|\
| * Disk free checking updatesEmile Joubert2012-03-261-6/+8
| | | | | | | | | | - add to status output - check supported platforms
View Lorry Controller Status