summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Merge pull request #160 from rabbitmq/rabbitmq-server-157Alvaro Videla2015-05-191-7/+9
|\ | | | | Start rabbit_alarm before FHC
| * Start rabbit_alarm before file_handle_cacheMichael Klishin2015-05-191-7/+9
|/ | | | | | | | | | | | | | Since the FHC now uses memory monitor, we need to make sure it is running early on. Nothing in rabbit_alarm really depends on the steps that used to run earlier. `full` test suite passes. It may be worth extracting memory and disk monitors into separate boot steps down the road. References #134. Fixes #157.
* RPM/deb changelogs for release 3.5.2rabbitmq_v3_5_2Jean-Sébastien Pédron2015-05-122-0/+9
|
* Merge pull request #153 from rabbitmq/rabbitmq-server-152Alvaro Videla2015-05-111-15/+74
|\ | | | | Support x-death event values from before #78
| * Re-format for 80 characters wideMichael Klishin2015-05-111-20/+25
| |
| * Re-format with EmacsMichael Klishin2015-05-111-27/+27
| |
| * Use a set to look up previously seen {queue, reason} keysMichael Klishin2015-05-101-15/+19
| | | | | | | | For O(1) lookup complexity.
| * RefactorMichael Klishin2015-05-101-4/+6
| |
| * RefactorMichael Klishin2015-05-101-23/+22
| |
| * Support x-death event proplists from before #78Michael Klishin2015-05-101-14/+63
| | | | | | | | | | We group x-death header values before processing them to make sure there's only one per {queue, reason}.
* | Merge branch 'rabbitmq-server-138' into stableJean-Sébastien Pédron2015-05-111-1/+6
|\ \ | |/ |/|
| * Make credit flow state transition interval 1s instead of 5sMichael Klishin2015-05-071-1/+6
|/ | | | | | | | | | | | | Management UI and HTTP API currently report connections and channels as in flow if they've been in flow for the last 5 seconds. That can confuse the user with inter-node flow control, making them believe the flow is permanent (it is not: the actual state toggles many times a second). This reduces the interval to 1s, which seems more reasonable and accurate (in a way). Fixes #138.
* Merge branch 'rabbitmq-server-129' into stableJean-Sébastien Pédron2015-05-071-1/+1
|\
| * rabbitmq-script-wrapper: Don't use "exec" in front of "su"Jean-Sébastien Pédron2015-04-231-1/+1
| | | | | | | | | | | | | | This is useless because su(1) forks a process anyway. Furthermore, it broke RabbitMQ in Docker. Fixes #129.
* | Merge pull request #146 from rabbitmq/rabbitmq-server-134Michael Klishin2015-05-072-6/+47
|\ \ | | | | | | PR for rabbitmq/rabbitmq-server#134
| * | File handle cache: Pay attention to memory useJean-Sébastien Pédron2015-05-062-6/+47
|/ / | | | | | | | | | | | | | | | | | | ... and clear read cache if necessary. This solves an issue where sync'ing a mirrored queue could take all available memory (way above the high watermark) and possibly crash the node. Fixes #134.
* | Merge branch 'rabbitmq-server-128' into stableJean-Sébastien Pédron2015-04-301-3/+21
|\ \
| * | rabbitmq-server: Add a way to send log messages to stdoutJean-Sébastien Pédron2015-04-301-3/+21
|/ / | | | | | | | | | | | | | | | | | | Now, by setting RABBITMQ_LOGS=-, regular log messages are written to stdout. Likewise, RABBITMQ_SASL_LOGS=- sends sasl log messages to stdout. This is useful for Docker images. Fixes #128.
* | Merge pull request #133 from rabbitmq/rabbitmq-server-114Michael Klishin2015-04-292-5/+15
|\ \ | |/ |/| Make gm flow control configurable
| * Reduce number of possible values of rabbit.mirroring_flow_controlMichael Klishin2015-04-292-4/+2
| |
| * Move mirroring flow control setting into rabbit_channel:initMichael Klishin2015-04-292-11/+14
| | | | | | | | | | Rename the key to make more sense, support true/false values.
| * Make gm flow control configurableMichael Klishin2015-04-162-2/+11
| | | | | | | | Fixes #114.
* | Merge branch 'rabbitmq-server-127' into stableJean-Sébastien Pédron2015-04-221-0/+15
|\ \
| * | rabbitmq-env: Ignore user's RABBITMQ_PID_FILE if set by init scriptJean-Sébastien Pédron2015-04-221-0/+15
|/ / | | | | | | | | | | | | | | | | | | | | The user shouldn't override the init script's RABBITMQ_PID_FILE value, otherwise the init script erroneously reports failures to start or stop the service. Now, rabbitmq-env logs a warning if RABBITMQ_PID_FILE is already defined in the environment (ie. by the init script) and in rabbitmq-env.conf. Fixes #127.
* | Merge branch 'rabbitmq-server-126' into stableJean-Sébastien Pédron2015-04-221-1/+1
|\ \
| * | Debian init script: Use $PID_FILE, not $RABBITMQ_PID_FILEJean-Sébastien Pédron2015-04-221-1/+1
|/ / | | | | | | | | | | ... because the latter is uninitialized in this script. Fixes #126.
* | Merge branch 'rabbitmq-server-120' into stableJean-Sébastien Pédron2015-04-211-2/+2
|\ \
| * | rabbitmq-env: Use "$path" in rmq_realpath(), not "$dir"Jean-Sébastien Pédron2015-04-211-2/+2
| | | | | | | | | | | | ... which does not exit.
* | | Merge branch 'rabbitmq-server-120' into stableJean-Sébastien Pédron2015-04-211-0/+57
|\ \ \ | |/ / | | / | |/ |/|
| * rabbitmq-env: Check the Mnesia directory is not used for other purposesJean-Sébastien Pédron2015-04-211-0/+57
|/ | | | | | | | | | | | | | | | If this is the case, log a warning to stderr. Here is an example with the plugins expansion directory: WARNING: RABBITMQ_PLUGINS_EXPAND_DIR is located inside RABBITMQ_MNESIA_DIR => Auto-clustering will not work ('cluster_nodes' in rabbitmq.config) And with the log directory: WARNING: RABBITMQ_LOG_BASE is equal to RABBITMQ_MNESIA_DIR RABBITMQ_LOGS is located inside RABBITMQ_MNESIA_DIR RABBITMQ_SASL_LOGS is located inside RABBITMQ_MNESIA_DIR => Auto-clustering will not work ('cluster_nodes' in rabbitmq.config) Fixes #120.
* adds start.boot to bin folder for mac-standalone releaseAlvaro Videla2015-04-151-0/+5
| | | | | | | This file is required by rabbit_nodes:ensure_epmd/0 in order to be able to programatically start epmd Fixes rabbitmq/rabbitmq-server#96
* adds OTP_VERSION to standalone macAlvaro Videla2015-04-151-0/+5
| | | | Fixes rabbitmq/rabbitmq-server#106
* Merge branch 'rabbitmq-management-33' into stableJean-Sébastien Pédron2015-04-101-0/+9
|\
| * Add rabbit_misc:get_env/3Michael Klishin2015-04-101-0/+9
|/ | | | | | | This is the same as application:get_env/3, but this one was only added to Erlang R16. References rabbitmq/rabbitmq-management#33.
* Merge branch 'rabbitmq-server-66' into stableJean-Sébastien Pédron2015-04-091-1/+1
|\
| * rabbitmq-script-wrapper: Escape '$' characters in argumentsJean-Sébastien Pédron2015-04-091-1/+1
|/ | | | Fixes #66.
* Commit package changelogs for 3.5.1Michael Klishin2015-04-032-0/+9
|
* Merge branch 'rabbitmq-server-86' into stablerabbitmq_v3_5_1Simon MacMullen2015-03-301-5/+9
|\
| * erase_ch/2 should return ctags for just the erased channel, not all of them.Simon MacMullen2015-03-301-5/+9
| | | | | | | | | | | | | | | | This was not noticed for a long time because the only use of those ctags was to emit consumer_deleted events which were handled by the management database, and it ignored invalid {channel, ctag} combinations. However, it did end up doing more work - and closing n channels out of m became O(nm) instead of just O(n). References #86.
* | Merge pull request #79 from rabbitmq/rabbitmq-server-78Jean-Sébastien Pédron2015-03-262-3/+58
|\ \ | | | | | | Limit x-death growth to one entry per queue
| * | rabbit_dead_letter.erl: Fix shadowing of variable 'Info'Jean-Sébastien Pédron2015-03-261-12/+18
| | | | | | | | | | | | | | | | | | While here, wrap long lines to fit 80 columns. References #78.
| * | Refactoring, x-death.counter => x-death.countMichael Klishin2015-03-262-34/+35
| | |
| * | Identify x-death events by {queue, reason}, add a counterMichael Klishin2015-03-251-17/+29
| | |
| * | Limit x-death growth to one entry per queueMichael Klishin2015-03-201-3/+39
| | | | | | | | | | | | | | | | | | Otherwise the list can grow forever in some cases. Fixes #78.
* | | Merge pull request #82 from rabbitmq/rabbitmq-server-72Jean-Sébastien Pédron2015-03-261-1/+1
|\ \ \ | | | | | | | | PR for rabbitmq/rabbitmq-server#72
| * | | rabbitmq-server.ocf: Pass ${RABBITMQ_PID_FILE} to "rabbitmqctl stop"Jean-Sébastien Pédron2015-03-251-1/+1
| | |/ | |/| | | | | | | | | | | | | Submitted by jmcmeek on GitHub. Fixes #72.
* | | Merge pull request #81 from rabbitmq/rabbitmq-server-74Michael Klishin2015-03-262-5/+7
|\ \ \ | |/ / |/| | PR for rabbitmq/rabbitmq-server#74
| * | Add 'channel' as a new log categoryJean-Sébastien Pédron2015-03-242-5/+7
|/ / | | | | | | | | | | | | | | | | | | | | | | For instance, one can use the following configuration to disable messages related to channels: [ {rabbit, [ {log_levels, [{channel, none}]} ]} ]. References #74.
* | Merge branch 'rabbitmq-server-69' into stableJean-Sébastien Pédron2015-03-231-23/+66
|\ \ | |/ |/|
| * Improvements to tune_read_buffer_limitSimon MacMullen2015-03-231-13/+25
| | | | | | | | | | | | | | | | Take into account the size of the current read if appropriate, add an extra byte when shrinking so next time we know how we did, and fix comments all round. References #69.
View Lorry Controller Status