summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* remove last vestiges of squarenessbug26126Matthias Radestock2014-04-171-2/+2
|
* O(n_queues^2) -> O(n_queues)Matthias Radestock2014-04-171-10/+7
| | | | Turns out the correct code is also simpler.
* Merge bug26118Simon MacMullen2014-04-163-6/+11
|\
| * cosmetic-ish: add a missing ?TABLE abstractionMatthias Radestock2014-04-161-4/+4
| |
| * cosmetic: prevent trailing whitespace in log messageMatthias Radestock2014-04-151-2/+2
| |
| * helper for starting a background rabbitMatthias Radestock2014-04-151-0/+5
| |
* | Handle hibernation in our pre-go state.bug26118Simon MacMullen2014-04-151-0/+3
|/
* Merge bug26115Simon MacMullen2014-04-151-4/+4
|\
| * eliminate accidental, crash-inducing assertionbug26115Matthias Radestock2014-04-141-4/+4
| |
* | Merge bug26113Simon MacMullen2014-04-151-1/+2
|\ \ | |/ |/|
| * Add a capability for it.bug26113Simon MacMullen2014-04-151-1/+2
|/
* Merge bug26084Simon MacMullen2014-04-142-41/+26
|\
| * eliminate comment duplicationMatthias Radestock2014-04-141-4/+1
| |
| * ensure propagation of master deathMatthias Radestock2014-04-131-8/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Previously slaves were monitoring the master and sending a process_death message through gm in an attempt to get the updated gm state propagated (and thus members_changed callbacks getting invoked on slaves, which in turn trigger promotion). However, the DOWN notification for the master may well arrive and be processed, and the process_death message sent around the ring, before GM has noticed the master death, thus rendering the process_death broadcast ineffectual for its intended purpose. With the recent GM changes we can guarantee that at least one slave will be notified of the master death via GM. So we emit the process_death message then, and not on master DOWN (and ditch the master monitoring as a result). Since the new emission is triggered by a gm notification we know GM is aware of the master death, thus avoiding the aforementioned problem.
| * less lazy death notificationsMatthias Radestock2014-04-131-21/+9
| | | | | | | | | | | | | | | | | | | | | | When we receive a DOWN, it's possible that there are no messages from the dead member floating around anyway. So rather than waiting for some other activity to occur first, it is perfectly safe enough to always call maybe_erase_aliases. That way we get slightly less lazy death notification in this case (i.e. we can then be certain that either the dead member is fully removed immediately or there must still be messages from the dead member floating around. No other possibility exists).
| * ensure callback_view_changed is called whenever the view may have changedMatthias Radestock2014-04-131-8/+8
| | | | | | | | | | | | We had missed a case here. Ditto for check_neighbours.
* | Merge bug26102Simon MacMullen2014-04-110-0/+0
|\ \ | |/
* | Actually let's move the unlink/1 back, not convinced it is any clearer.bug26102Simon MacMullen2014-04-111-5/+4
| |
* | Monitor and wait for 'DOWN' from our own GM as well as the slaves, to make ↵Simon MacMullen2014-04-101-5/+6
|/ | | | sure our GM does not try to update group info after we have called forget_group/1. Also ensure we unlink from the coordinator when shutting down as well as when stopping mirroring, not strictly necessary but clearer.
* update copyright notice yearMatthias Radestock2014-04-101-1/+1
|
* Merge bug25855Simon MacMullen2014-04-094-17/+34
|\
| * More unique atombug25855Simon MacMullen2014-04-091-2/+2
| |
| * Delayed restart of the disk monitor.Simon MacMullen2014-04-093-12/+25
| |
| * Make sure we have complete command output if we actually can't parse it.Simon MacMullen2014-04-091-5/+9
| |
* | Merge bug26100Simon MacMullen2014-04-092-8/+12
|\ \ | |/
| * Merge bug26103Simon MacMullen2014-04-091-1/+1
| |\
| | * Merge bug26104Simon MacMullen2014-04-091-1/+1
| | |\
| | | * That ~s should not be there.bug26104Simon MacMullen2014-04-091-1/+1
| | |/
| * | Maybe simplerbug26103Simon MacMullen2014-04-091-7/+7
| | |
| * | Only allow cycles that contain reject.Simon MacMullen2014-04-081-13/+17
| |/
* | Oopsbug26100Simon MacMullen2014-04-091-1/+4
| |
* | OopsSimon MacMullen2014-04-081-2/+2
| |
* | Allow parameter validation to know about the user making the change.Simon MacMullen2014-04-086-25/+34
|/
* Merge bug 26098Simon MacMullen2014-04-081-3/+24
|\
| * Merge bug26096Simon MacMullen2014-04-041-3/+24
| |\
| | * Improve diagnostics when the node is up.bug26096Simon MacMullen2014-04-031-3/+24
| | |
* | | Bring back impersonator tag.bug26098Simon MacMullen2014-04-041-4/+8
|/ /
* | default to stableSimon MacMullen2014-04-020-0/+0
|\ \ | |/ |/|
* | Changelog for 3.3.0.Simon MacMullen2014-04-022-0/+9
| |
* | Added tag rabbitmq_v3_3_0 for changeset b07baed34a12Simon MacMullen2014-04-020-0/+0
| |
* | Merge headsrabbitmq_v3_3_0Simon MacMullen2014-04-022-7/+18
|\ \
| * \ Merge bug26094Simon MacMullen2014-04-020-0/+0
| |\ \
| * | | Remove some generated files so we can build twice.bug26094Simon MacMullen2014-04-021-0/+3
| |/ /
| * | Merge bug26092Simon MacMullen2014-04-020-0/+0
| |\ \
| * | | Updates for the new way of doing mandatory.bug26092Simon MacMullen2014-04-021-7/+15
| |/ /
* | | merge bug26093 into defaultMatthias Radestock2014-04-020-0/+0
|\ \ \ | |/ /
* | | remove DM-Upload-Allowed, as per new debian policybug26093Matthias Radestock2014-04-021-1/+0
|/ /
* | Merge bug 25786Simon MacMullen2014-04-010-0/+0
|\ \
* | | Cosmeticbug25786Simon MacMullen2014-04-011-7/+7
| | |
* | | Events for login success / failure.Simon MacMullen2014-04-011-18/+23
| | |
View Lorry Controller Status