summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Cope with the fact that rabbit_mnesia:running_clustered_nodes/0 now does not ↵Simon MacMullen2012-09-171-2/+11
| | | | include node() during boot.
* Merge defaultSimon MacMullen2012-09-179-134/+271
|\
| * Merge defaultSimon MacMullen2012-09-149-134/+271
| |\
| | * cosmeticMatthias Radestock2012-09-051-4/+2
| | |
| | * Also exclude DeadNodes from the list of new nodes to start mirrors on; we ↵Simon MacMullen2012-09-051-1/+1
| | | | | | | | | | | | have checked for running_clustered_nodes() but that could be out of date.
| | * Cosmetic: give that comment room to breath.Simon MacMullen2012-09-051-20/+21
| | |
| | * Call add_mirror/2 before drop_mirror/2, and explain why.Simon MacMullen2012-09-051-1/+11
| | |
| | * GahSimon MacMullen2012-09-052-4/+2
| | |
| | * No we don't. The point is that if a mirror is dropping out of the queue, ↵Simon MacMullen2012-09-052-2/+0
| | | | | | | | | | | | does it need to explicitly leave the GM group? The answer is no: the master is linked to the coordinator is linked to the GM / the slave is linked to the GM.
| | * Add specs, remove misleading "%% temp" comment.Simon MacMullen2012-09-053-9/+15
| | |
| | * Reduce difference to defaultSimon MacMullen2012-09-051-3/+3
| | |
| | * merge default into bug24908Matthias Radestock2012-09-049-136/+262
| | |\
| | | * more reification, plus cosmeticsMatthias Radestock2012-09-041-18/+13
| | | |
| | | * Reify a touch more.Simon MacMullen2012-09-041-5/+6
| | | |
| | | * Suggest queue nodes based on running nodes, otherwise (at the very least) we ↵Simon MacMullen2012-08-231-1/+2
| | | | | | | | | | | | | | | | can immediately try to start a mirror on a node that has just gone down.
| | | * Fix broken mergeSimon MacMullen2012-08-231-2/+2
| | | |
| | | * s/at-least/exactly/gSimon MacMullen2012-08-222-12/+12
| | | |
| | | * Merge defaultSimon MacMullen2012-08-2110-173/+169
| | | |\
| | | * | at-least mode can imply that we need to start slaves in response to slaves ↵Simon MacMullen2012-08-171-10/+30
| | | | | | | | | | | | | | | | | | | | dying elsewhere. So do that.
| | | * | Merge defaultSimon MacMullen2012-08-159-125/+234
| | | |\ \
| | | | * | Reify something that was previously a little bit magic.Simon MacMullen2012-08-072-6/+13
| | | | | |
| | | | * | Support changing master (umm, which actually turned out to be a lot easier ↵Simon MacMullen2012-08-071-10/+7
| | | | | | | | | | | | | | | | | | | | | | | | than expected, thanks Matthew).
| | | | * | Take account of the current nodes when selecting new nodes, and some unit ↵Simon MacMullen2012-08-072-29/+70
| | | | | | | | | | | | | | | | | | | | | | | | tests for the node selection logic.
| | | | * | Merge in defaultSimon MacMullen2012-08-078-120/+184
| | | | |\ \
| | | | | * | Various fixes.Simon MacMullen2012-07-092-17/+9
| | | | | | |
| | | | | * | Merge bug25048Simon MacMullen2012-07-098-123/+195
| | | | | |\ \
| | | | | | * \ Merge bug25048Simon MacMullen2012-07-098-123/+195
| | | | | | |\ \
| | | | | | | * | Dynamic change of HA policy. Promotion from non-HA to master, and demotion ↵Simon MacMullen2012-07-065-32/+112
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | from master to non-HA as appropriate. There will still be problems if the policy changes such that the master needs to change - I'm not sure we should even allow this.
| | | | | | | * | Rename function, remove utter rubbish.Simon MacMullen2012-07-063-15/+15
| | | | | | | | |
| | | | | | | * | Rough sketch of dynamic queue HA-ness:Simon MacMullen2012-07-057-92/+89
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * Remove #amqqueue.mirror_nodes, we will always derive this from policy * Remove everything to do with x-ha-* arguments * Abstract a bit more stuff into rabbit_mirror_queue_misc * Add a new "at-least" mode This works! Sort of. Changing policies on the fly, changing HAness altogether, having "at-least" set up a new mirror when one disappears, and probably some other things do not work.
* | | | | | | | | file_name -> filenameMatthias Radestock2012-09-174-26/+26
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The latter is used in more places and also by OTP. In the process fix a bug - rabbit_upgrade was referencing rabbit_node_monitor:running_nodes_filename/0, which was in fact named running_nodes_file_name. That function was also missing a spec. And it was in the "wrong" place w.r.t. the function order in the module ;)
* | | | | | | | | merge bug25154 into defaultMatthias Radestock2012-09-170-0/+0
|\ \ \ \ \ \ \ \ \
| * \ \ \ \ \ \ \ \ merge bug25154 into defaultMatthias Radestock2012-09-171-5/+5
| |\ \ \ \ \ \ \ \ \ | | |/ / / / / / / / | |/| | | | | | | |
* | | | | | | | | | 1MB = 1000000B for disksMatthias Radestock2012-09-171-1/+1
| |/ / / / / / / / |/| | | | | | | |
* | | | | | | | | correct disk space log message and remove ambiguityMatthias Radestock2012-09-171-5/+5
|/ / / / / / / /
* | | | | | | | Merge bug24914Simon MacMullen2012-09-145-105/+127
|\ \ \ \ \ \ \ \
| * \ \ \ \ \ \ \ merge bug25118 into defaultTim Watson2012-09-145-105/+127
| |\ \ \ \ \ \ \ \
| | * \ \ \ \ \ \ \ merge default into bug25118Tim Watson2012-09-145-105/+127
| | |\ \ \ \ \ \ \ \ | |/ / / / / / / / /
| | * | | | | | | | updated the essay to explain how the sync status works nowFrancesco Mazzoli2012-09-131-19/+25
| | | | | | | | | |
| | * | | | | | | | two little fixes...Francesco Mazzoli2012-09-061-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | It turns out that the problems I had with the kill-multi test on default was because the messages were start publishing right after the queue was created. I thought that once queue.declare returned, it meant that the queue was present on all nodes, but it wasn't, and for this reason we had the mismatching messages and the purging. Once I discovered that, I went back two my code and immediately discovered two very silly mistakes. I feel silly as well now. I think that bug 25130 still has a reason to extist, but I wouldn't worry about it now.
| | * | | | | | | | cosmeticsFrancesco Mazzoli2012-09-041-1/+1
| | | | | | | | | |
| | * | | | | | | | cosmeticsFrancesco Mazzoli2012-09-042-4/+1
| | | | | | | | | |
| | * | | | | | | | cosmeticsFrancesco Mazzoli2012-09-041-1/+1
| | | | | | | | | |
| | * | | | | | | | merge defaultFrancesco Mazzoli2012-09-047-110/+222
| | |\ \ \ \ \ \ \ \
| | * | | | | | | | | remove differences with defaultFrancesco Mazzoli2012-09-041-10/+12
| | | | | | | | | | |
| | * | | | | | | | | track the delta of the depths, and replace `pending_ack' with `depth' in BQFrancesco Mazzoli2012-09-044-71/+52
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The kill-multi test is still failing...
| | * | | | | | | | | was getting `set_length' instead of `drop'Francesco Mazzoli2012-09-041-1/+1
| | | | | | | | | | |
| | * | | | | | | | | fix depth delta in the `publish' instructionFrancesco Mazzoli2012-09-041-1/+1
| | | | | | | | | | |
| | * | | | | | | | | forgot debug line inFrancesco Mazzoli2012-09-031-1/+0
| | | | | | | | | | |
| | * | | | | | | | | store the depth of master and slave instead of the unknown pending msgsFrancesco Mazzoli2012-09-032-69/+92
| | | | | | | | | | |
View Lorry Controller Status