| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | beta->delta conversion rate is naturally limited | Matthias Radestock | 2014-03-04 | 1 | -9/+11 |
| | | | | | | which means we don't need an explicit upper bound, which in turn would have required some interaction with q_process. | ||||
| * | increase IO_BATCH_SIZE | Matthias Radestock | 2014-03-04 | 1 | -7/+7 |
| | | | | | | | | | ...so that beta->gamma conversion can keep up with alpha->beta conversion. Also correct comment - beta->gamma conversion can happen in a lot more places than 'publish' | ||||
| * | reduce_memory_use now only does one thing | Matthias Radestock | 2014-03-03 | 1 | -37/+12 |
| | | |||||
| * | propagate BQ API change | Matthias Radestock | 2014-03-03 | 2 | -2/+9 |
| | | |||||
| * | explain (reduced) impact of IO_BATCH_SIZE | Matthias Radestock | 2014-03-03 | 1 | -14/+7 |
| | | |||||
| * | decouple syncing from paging | Matthias Radestock | 2014-03-03 | 2 | -22/+14 |
| | | |||||
| * | merge in default | Matthias Radestock | 2014-03-03 | 1 | -2/+3 |
| |\ | |||||
| | * | merge bug26049 into default | Matthias Radestock | 2014-03-03 | 0 | -0/+0 |
| | |\ | |||||
| | * | | clamp duration to infinity when all rates are very low | Matthias Radestock | 2014-03-03 | 1 | -2/+3 |
| | |/ | | | | | | | | | ...so that the memory monitor excludes the queue from avg duration calculations, which would otherwise get massively skewed. | ||||
| * | | limit alpha->beta conversion through msg store credit flow | Matthias Radestock | 2014-03-03 | 2 | -16/+23 |
| |/ | | | | | | | we also bump the IO_BATCH_SIZE; it's only used to limit beta->gamma conversion, which is a fairly cheap operation (it only touches qi, which has a very compact on-disk representation), and we want to make sure that such conversion can keep up with the alpha->beta conversion. | ||||
| * | Merge bug26042 | Simon MacMullen | 2014-02-28 | 3 | -16/+22 |
| |\ | |||||
| | * | Make mirrored queue logging configurable. | Simon MacMullen | 2014-02-27 | 3 | -16/+22 |
| |/ | |||||
| * | Merge bug26027 | Simon MacMullen | 2014-02-26 | 0 | -0/+0 |
| |\ | |||||
| * \ | Merge in default | Simon MacMullen | 2014-02-26 | 2 | -9/+14 |
| |\ \ | |/ | |||||
| | * | stable to default | Simon MacMullen | 2014-02-26 | 60 | -1845/+2774 |
| | |\ | |||||
| | | * | Merge bug26039 | Simon MacMullen | 2014-02-26 | 1 | -8/+2 |
| | | |\ | |||||
| | | | * | Don't quote node atoms, it makes the resulting string harder to use in shell ↵ | Simon MacMullen | 2014-02-26 | 1 | -8/+2 |
| | | |/ | | | | | | | | | | scripts. | ||||
| | * | | Merge bug 26038 | Simon MacMullen | 2014-02-26 | 1 | -1/+12 |
| | |\ \ | |||||
| | | * | | If we abandon autoheal while in winner_waiting then let the losing nodes ↵ | Simon MacMullen | 2014-02-26 | 1 | -1/+12 |
| | |/ / | | | | | | | | | | know they can carry on. | ||||
| * | | | Update comment. | Simon MacMullen | 2014-02-26 | 1 | -4/+7 |
| | | | | |||||
| * | | | Eliminate the node_stopped message, since it is possible that a badly-timed ↵ | Simon MacMullen | 2014-02-26 | 2 | -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 MacMullen | 2014-02-26 | 1 | -13/+9 |
| | | | | | | | | | handle_dead_rabbit_state is not very useful. | ||||
| * | | Merge bug 26004 | Simon MacMullen | 2014-02-24 | 1 | -20/+26 |
| |\ \ | |||||
| | * | | trigger rate calculation in all the right places | Matthias Radestock | 2014-02-07 | 1 | -20/+26 |
| | | | | |||||
| * | | | Merge bug25994 | Simon MacMullen | 2014-02-24 | 1 | -2/+11 |
| |\ \ \ | |||||
| | * | | | Sort by descending priority order, and add a comment. | Simon MacMullen | 2014-02-24 | 1 | -2/+11 |
| | | | | | |||||
| | * | | | always prioritise acks (and resume) | Matthias Radestock | 2014-02-24 | 1 | -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. | ||||
| * | | | | merge stable into default | Matthias Radestock | 2014-02-24 | 1 | -32/+44 |
| |\ \ \ \ | |/ / / |/| | / | | |/ | |/| | |||||
| | * | | merge bug26013 into stable | Matthias Radestock | 2014-02-24 | 1 | -32/+44 |
| | |\ \ | |||||
| | | * | | improve clarity and correctness | Matthias Radestock | 2014-02-20 | 1 | -30/+38 |
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | - introduce blocked_by_alarm state predicate which makes it easier / more obvious to detect the transitions to/from - do not send 'unblocked' when the client doesn't have the capability - ditch superfluous true/false return from maybe_send_unblocked (now send_unblocked) - detect the transition into blocked_by_alarm that can result from handling conserve_resources (the original purpose of the bug) | ||||
| | | * | | Eliminate a compiler warning | Michael Klishin | 2014-02-19 | 1 | -1/+1 |
| | | | | | |||||
| | | * | | Send connection.unblocked when connection is no longer blocked or all alarms ↵ | Michael Klishin | 2014-02-19 | 1 | -1/+4 |
| | | | | | | | | | | | | | | | | | clear | ||||
| | | * | | Make connection.[un]blocked independent from flow control | Michael Klishin | 2014-02-19 | 1 | -16/+17 |
| | | | | | |||||
| * | | | | Bug 25939 broke AMQP 1.0; fix it. | Simon MacMullen | 2014-02-19 | 1 | -1/+1 |
| | | | | | |||||
| * | | | | stable to default | Simon MacMullen | 2014-02-19 | 60 | -1809/+2733 |
| |\ \ \ \ | |/ / / |/| | | | |||||
| | * | | | Merge bug26022 | Simon MacMullen | 2014-02-19 | 0 | -0/+0 |
| | |\ \ \ | |||||
| | * | | | | Add LDAP timeout to example config | Simon MacMullen | 2014-02-19 | 1 | -0/+4 |
| | |/ / / | |||||
| | * | | | cosmetic | Matthias Radestock | 2014-02-18 | 1 | -3/+3 |
| | | | | | |||||
| | * | | | merge bug25868 into default | Matthias Radestock | 2014-02-18 | 0 | -0/+0 |
| | |\ \ \ | |||||
| | | * \ \ | Merge bug25868 (again) | Simon MacMullen | 2014-02-18 | 1 | -5/+4 |
| | | |\ \ \ | |||||
| | | * \ \ \ | Merge bug25868 | Simon MacMullen | 2014-02-18 | 0 | -0/+0 |
| | | |\ \ \ \ | |||||
| | * | | | | | | clearer | Matthias Radestock | 2014-02-18 | 1 | -5/+7 |
| | | |_|/ / / | |/| | | | | | | | | | | | | | | | | I think | ||||
| | * | | | | | Only ever return 'flow' if there are no alarms. I think in theory it's not ↵ | Simon MacMullen | 2014-02-18 | 1 | -5/+4 |
| | |/ / / / | | | | | | | | | | | | | | | | possible for there to be an alarm when in flow control, but this is more correct and no less clear. | ||||
| | * | | | | Oops | Simon MacMullen | 2014-02-17 | 1 | -1/+0 |
| | | | | | | |||||
| | * | | | | ...but only do that if we are not also alarmed. | Simon MacMullen | 2014-02-17 | 1 | -2/+4 |
| | | | | | | |||||
| | * | | | | Show state as 'flow' if we are currently flow blocked and have been so for ↵ | Simon MacMullen | 2014-02-17 | 2 | -6/+8 |
| | |/ / / | | | | | | | | | | | | | more than 5s. | ||||
| | * | | | Merge bug25627 (again) | Simon MacMullen | 2014-02-17 | 48 | -1097/+1628 |
| | |\ \ \ | |||||
| | | * \ \ | Merge bug25627 | Simon MacMullen | 2014-02-17 | 1 | -1/+7 |
| | | |\ \ \ | |||||
| | | * \ \ \ | stable to default | Simon MacMullen | 2014-02-17 | 2 | -8/+10 |
| | | |\ \ \ \ | | | | |/ / | | | |/| | | |||||
| | | * | | | | merge bug25853 into default | Matthias Radestock | 2014-02-13 | 3 | -49/+66 |
| | | |\ \ \ \ | |||||
