summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* correctness++bug26066Matthias Radestock2014-03-131-1/+1
|
* turns out that cleaning up 'clients' in client_terminate is badMatthias Radestock2014-03-131-6/+6
| | | | | since it breaks clean shutdown/recovery, which relies on the CRefs in 'clients'.
* invoke credit_flow:peer_down on, err, DOWN. *only*Matthias Radestock2014-03-131-8/+11
| | | | | | | | Thus preventing potential leaks and deadlocks. Also, clean up 'clients' in clear_client, and thus client_terminate, which was previously missing and thus the source of another potential leak.
* stable to defaultSimon MacMullen2014-03-111-3/+4
|\
| * Merge bug 26063Simon MacMullen2014-03-110-0/+0
| |\
| * | Don't corrupt the node montor state even if we are about to shut down.bug26063Simon MacMullen2014-03-111-3/+4
| |/
* | Be a tiny bit more correctSimon MacMullen2014-03-101-1/+1
| |
* | stable to defaultSimon MacMullen2014-03-101-3/+2
|\ \ | |/
| * Merge bug26058Simon MacMullen2014-03-101-3/+2
| |\
| | * Fix memory calculations: we were erroneously removing the mgmt db from the ↵bug26058Simon MacMullen2014-03-101-3/+2
| |/ | | | | | | plugins bucket (although it was never counted there) and not removing it from the 'other plugins' bucket (although it was).
* | Merge bug25957 (again)Simon MacMullen2014-03-077-22/+67
|\ \
| * \ Merge bug25957Simon MacMullen2014-03-066-116/+196
| |\ \
| * \ \ Merge bug26056Simon MacMullen2014-03-060-0/+0
| |\ \ \
| * | | | Start the consumer utilisation average at active 100% of the time, since ↵bug26056Simon MacMullen2014-03-061-1/+1
| |/ / / | | | | | | | | | | | | when we first add a first consumer it will not be blocked.
| * | | Merge bug25603Simon MacMullen2014-03-054-21/+57
| |\ \ \
| | * \ \ Merge in defaultbug25603Simon MacMullen2014-02-244-21/+57
| | |\ \ \
| | | * | | OopsSimon MacMullen2014-02-181-1/+1
| | | | | |
| | | * | | Allow checking an IP address as well as a socket.Simon MacMullen2014-02-183-13/+13
| | | | | |
| | | * | | Refuse access for guest via non-localhost by default.Simon MacMullen2014-02-144-21/+57
| | | | | |
| * | | | | stable to defaultSimon MacMullen2014-03-0461-1883/+2822
| |\ \ \ \ \ | | |_|_|_|/ | |/| | | |
| * | | | | Added tag rabbitmq_v3_2_4 for changeset d44905fa517aSimon MacMullen2014-03-040-0/+0
| | | | | |
| * | | | | Package changelogs for 3.2.4.rabbitmq_v3_2_4Simon MacMullen2014-03-042-0/+9
| | | | | |
| * | | | | Added tag rabbitmq_v3_2_4 for changeset b93445fda35cSimon MacMullen2014-03-040-0/+0
| | | | | |
* | | | | | Update APIbug25957Simon MacMullen2014-03-071-1/+1
| |_|_|_|/ |/| | | |
* | | | | Rename info itemsSimon MacMullen2014-03-062-4/+8
| | | | |
* | | | | Strip out support for x-prefetch.Simon MacMullen2014-03-043-8/+2
| | | | |
* | | | | Management information on per-consumer prefetchSimon MacMullen2014-03-044-31/+42
| | | | |
* | | | | Change the semantics of the basic.qos global flag to switch between ↵Simon MacMullen2014-03-044-31/+45
| | | | | | | | | | | | | | | | | | | | per-consumer and per-channel prefetch.
* | | | | Merge in defaulbug24297Simon MacMullen2014-03-041-7/+7
|\ \ \ \ \ | | |/ / / | |/| | |
| * | | | OopsSimon MacMullen2014-03-041-7/+7
| | | | |
* | | | | Merge in defaultSimon MacMullen2014-03-0410-129/+166
|\ \ \ \ \ | |/ / / /
| * | | | merge bug26049 into defaultMatthias Radestock2014-03-030-0/+0
| |\ \ \ \
| * | | | | clamp duration to infinity when all rates are very lowbug26049Matthias Radestock2014-03-031-2/+3
| |/ / / / | | | | | | | | | | | | | | | | | | | | ...so that the memory monitor excludes the queue from avg duration calculations, which would otherwise get massively skewed.
| * | | | Merge bug26042Simon MacMullen2014-02-283-16/+22
| |\ \ \ \
| | * | | | Make mirrored queue logging configurable.bug26042Simon MacMullen2014-02-273-16/+22
| |/ / / /
| * | | | Merge bug26027Simon MacMullen2014-02-260-0/+0
| |\ \ \ \
| * \ \ \ \ Merge in defaultbug26027Simon MacMullen2014-02-262-9/+14
| |\ \ \ \ \ | | |/ / / /
| | * | | | stable to defaultSimon MacMullen2014-02-2660-1845/+2774
| | |\ \ \ \ | | | |/ / / | | |/| | |
| | | * | | Merge bug26039Simon MacMullen2014-02-261-8/+2
| | | |\ \ \
| | | | * | | Don't quote node atoms, it makes the resulting string harder to use in shell ↵bug26039Simon MacMullen2014-02-261-8/+2
| | | |/ / / | | | | | | | | | | | | | | | | | | scripts.
| | * | | | Merge bug 26038Simon MacMullen2014-02-261-1/+12
| | |\ \ \ \
| | | * | | | If we abandon autoheal while in winner_waiting then let the losing nodes ↵bug26038Simon MacMullen2014-02-261-1/+12
| | |/ / / / | | | | | | | | | | | | | | | | | | know they can carry on.
| * | | | | Update comment.Simon MacMullen2014-02-261-4/+7
| | | | | |
| * | | | | Eliminate the node_stopped message, since it is possible that a badly-timed ↵Simon MacMullen2014-02-262-22/+22
| | |/ / / | |/| | | | | | | | | | | | | stop_app could lead to us missing it. Instead just go based on whether the rabbit stops - if it stops for any reason other than autoheal, we just send it a message it will ignore and continue.
| * | | | Refactor: distinction between handle_dead_rabbit and ↵Simon MacMullen2014-02-261-13/+9
| | | | | | | | | | | | | | | | | | | | handle_dead_rabbit_state is not very useful.
| * | | | Merge bug 26004Simon MacMullen2014-02-241-20/+26
| |\ \ \ \ | | |_|/ / | |/| | |
| | * | | trigger rate calculation in all the right placesbug26004Matthias Radestock2014-02-071-20/+26
| | | | |
| * | | | Merge bug25994Simon MacMullen2014-02-241-2/+11
| |\ \ \ \
| | * | | | Sort by descending priority order, and add a comment.bug25994Simon MacMullen2014-02-241-2/+11
| | | | | |
| | * | | | always prioritise acks (and resume)Matthias Radestock2014-02-241-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The former, so that we preserve ack ordering which, while of no semantic relevance, is good for performance since it allows us to optimise for the common acks-in-order case. The latter since it unblocks a queue from delivering messages and thus is conducive to keeping queue lengths short. We prioritise acks higher than most other messages since they are the only high-frequency message which is guaranteed to free up resources. Prioritising ack and resume all the time is safe since flow control places an upper bound on how many of these we can get, thus preventing starvation of senders of lower-priority messages.
View Lorry Controller Status