summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Set ra wal_max_size_bytes default if not setkjnilsson2019-06-241-0/+6
| | | | To match it in unit with the rest of rabbit.
* pass metrics keykjnilsson2019-06-201-0/+1
|
* Delete server if add_member failskjnilsson2019-06-181-1/+1
| | | | Addressing a TODO of that effect.
* Replace spaces by underscores when forging module nameArnaud Cogoluègnes2019-06-141-1/+3
| | | | | | | | | | | | Plugins can provide a module to be called to extract extra information at authentication time. The module name is based on the protocol used. Some protocols have a space in their name, like "Web MQTT", so spaces in such cases must be replaced by underscores to come up with a valid Erlang module name. [#166271318] References #1767
* Merge pull request #1982 from rabbitmq/rabbitmq_prelaunch_ipv6Luke Bakken2019-06-131-0/+1
|\ | | | | Workaround for IPv6 EPMD
| * Add RABBITMQ_SERVER_ADDITIONAL_ERL_ARGSGabriele2019-05-311-0/+1
| | | | | | | | | | With this patch it is possible to pass variables to prelaunch state.
* | Merge pull request #2034 from rabbitmq/rabbitmq-server-2030D Corbacho2019-06-132-0/+15
|\ \ | | | | | | Make default worker pool size configurable
| * | Make default worker pool size configurableMichael Klishin2019-06-132-0/+15
|/ / | | | | | | Part of rabbitmq/rabbitmq-server#2030.
* | Merge pull request #2033 from rabbitmq/rabbitmq-cli-330Michael Klishin2019-06-131-1/+16
|\ \ | | | | | | Schema information in mnesia for cli command
| * | Schema information in mnesia for cli commandDiana Corbacho2019-06-131-1/+16
| | | | | | | | | | | | [#164550205]
* | | amqqueue*: Uniformize APIJean-Sébastien Pédron2019-06-132-14/+277
| | | | | | | | | | | | | | | | | | Now, both modules export the same set of functions. This will help with the backport to `v3.7.x` and thus the life of plugin developers who will not have to have one copy of their plugin per RabbitMQ version.
* | | include/amqqueue.hrl: Fix indentationJean-Sébastien Pédron2019-06-131-9/+9
| | |
* | | Merge pull request #2031 from rabbitmq/rabbitmq-shovel-60Michael Klishin2019-06-131-0/+25
|\ \ \ | |/ / |/| | Update log configuration tests for rabbitmq/rabbitmq-common#328
| * | Update log configuration tests for rabbitmq/rabbitmq-common#328Michael Klishin2019-06-121-0/+25
|/ /
* | Head message timestamp: make the test more robustMichael Klishin2019-06-111-4/+16
| |
* | Reference a public IPv4 that has a PTR recordGerhard Lazu2019-06-101-9/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Public IPv6 192.240.153.117 is managed by OVH US and has a PTR 117.153.240.192.in-addr.arp record that resolves to www.rabbitmq.com. It would be nice to move to an IPv4 & IPv6 that are managed by our wider org. dig 117.153.240.192.in-addr.arpa PTR +short www.rabbitmq.com. whois 192.240.153.117 | grep -i Organiz Organization: OVH US LLC (OUL-16) cc @michaelklishin @trevormarshall
* | Merge pull request #2019 from ↵Michael Klishin2019-06-075-46/+71
|\ \ | | | | | | | | | | | | rabbitmq/rabbitmq-server-1767-protocol-specific-ctx-in-authn-authz Propagate protocol-specific context to authorization
| * \ Merge branch 'master' into ↵Michael Klishin2019-06-0716-81/+224
| |\ \ | |/ / |/| | | | | rabbitmq-server-1767-protocol-specific-ctx-in-authn-authz
* | | Handle rejected queues on confirm.queue_confirm_refactorDaniil Fedotov2019-06-043-29/+34
| | | | | | | | | | | | | | | | | | | | | When one queue confirms a message and another queue failed without confirming it, the message should be rejected. Fixes some races between confirms and rejects.
* | | Switch msg_id_to_channel from gb_tree to maps.Daniil Fedotov2019-06-042-14/+12
| | |
* | | Reject a message before discarding it from BQ.Daniil Fedotov2019-06-041-3/+10
| | | | | | | | | | | | | | | discard/4 confirms a message, which can cause races between confirms and rejects.
* | | Merge pull request #2022 from rabbitmq/ra-metricsMichael Klishin2019-06-042-0/+13
|\ \ \ | | | | | | | | Add channel info for pending raft commands
| * | | Add channel info for pending raft commandskjnilsson2019-06-042-0/+13
| | | | | | | | | | | | | | | | [#165184345]
* | | | Update rabbitmq-components.mkGerhard Lazu2019-06-031-1/+1
| | | |
* | | | Type fixes to keep dialyzer happyDaniil Fedotov2019-05-292-3/+3
| | | |
* | | | Merge pull request #2018 from rabbitmq/rabbitmq-cli-302Michael Klishin2019-05-292-2/+26
|\ \ \ \ | | | | | | | | | | 'check' function for health check of virtual hosts
| * | | | 'check' function for health check of virtual hostsDiana Corbacho2019-05-282-2/+26
| | | | | | | | | | | | | | | | | | | | [#163451547]
* | | | | Merge pull request #2015 from Invizory/dead-letter-rejected-publishedDaniil Fedotov2019-05-298-34/+130
|\ \ \ \ \ | | | | | | | | | | | | Add an option to dead-letter rejected publishes
| * | | | | Add remaining tests for `reject-publish-dlx`Arthur Khashaev2019-05-283-15/+43
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Add tests for `reject-publish-dlx` overflow strategy for all corresponding tests for `reject-publish` strategy. The tests are grouped to avoid code duplication. See #1443
| * | | | | Add overflow tests to `confirms_rejects_SUITE`Arthur Khashaev2019-05-281-13/+35
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This change splits the tests into groups for both the existing `reject-publish` overflow strategy and the new `reject-publish-dlx`. The corresponding queue names have been suffixed to make the tests in the groups independent and thus parallel. See #1443
| * | | | | Add an option to dead-letter rejected publishesArthur Khashaev2019-05-274-6/+52
|/ / / / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Add `reject-publish-dlx` overflow strategy, which is similar to `reject-publish` strategy, but also dead-letters rejected messages. Closes #1443
| | | * | Be more tolerant in rabbit_channel:get_amqp_params/2Arnaud Cogoluègnes2019-06-071-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The function can be called outside of any AMQP connection (e.g. from the management plugin), so trying to get any protocol-specific information from the connection state does not make much sense. References #1767
| | | * | Propagate protocol-specific context to authorizationArnaud Cogoluègnes2019-05-295-45/+69
| |_|/ / |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Propagate protocol-specific context like MQTT client ID to authentication and authorization backends. The propagation was already there for topic authorization. Resource check needed propagation and a new argument in the backend function. Virtual host check just needed propagation, as there was already a context parameter (for peer address). A context parameter and propagation was already there for login-related functions. Unfortunately the context API is not fully consistent, due to historical reasons: proplists are the historical data structure, maps are used whenever possible. References #1767
* | | | Improving confirms test stability and error reportingDaniil Fedotov2019-05-271-3/+10
| | | | | | | | | | | | | | | | | | | | | | | | Add process messages to the error message. Try harder to kill queues.
* | | | Improve error handling and increase timeout in confirm-reject testDaniil Fedotov2019-05-271-3/+4
| |/ / |/| | | | | | | | | | | This is to prevent false-positives on slow systems and detect genuine errors better.
* | | Merge pull request #2014 from rabbitmq/quorum-statusMichael Klishin2019-05-231-9/+41
|\ \ \ | | | | | | | | Improve quorum_status command
| * | | Improve quorum_status commandkjnilsson2019-05-231-9/+41
| | | | | | | | | | | | | | | | Make it compatible with the pretty table formatter.
* | | | Update rabbitmq-components.mkJean-Sébastien Pédron2019-05-171-1/+1
| | | |
* | | | Update rabbitmq-components.mkMichael Klishin2019-05-171-1/+1
| | | |
* | | | Update rabbitmq-components.mkMichael Klishin2019-05-161-2/+2
| | | |
* | | | Merge pull request #2011 from ↵Michael Klishin2019-05-151-2/+2
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | rabbitmq/fix-notify-limiter-after-consumer-timeout-change Adapt clause in notify_limiter to consumer timeout changes
| * | | | Adapt clause in notify_limiter to consumer timeout changesArnaud Cogoluègnes2019-05-151-2/+2
|/ / / /
* | | | Update rabbitmq-components.mkMichael Klishin2019-05-141-1/+1
| | | |
* | | | Add a dependency on observer_cli, closes #2006Michael Klishin2019-05-131-1/+1
| | | |
* | | | Update rabbitmq-components.mkMichael Klishin2019-05-131-0/+1
| | | |
* | | | Merge pull request #1893 from rabbitmq/do_not_confirm_on_unreachable_queueMichael Klishin2019-05-134-244/+478
|\ \ \ \ | | | | | | | | | | Make sure that publishes to dead or unaccessible queues return nack
| * | | | CosmeticsMichael Klishin2019-05-131-1/+1
| | | | |
| * | | | CosmeticsMichael Klishin2019-05-131-4/+4
| | | | |
| * | | | CosmeticsMichael Klishin2019-05-131-50/+38
| | | | |
| * | | | Change publisher confirms behaviour to reject messages if no queues confirmed.Daniil Fedotov2019-05-104-242/+488
|/ / / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Channel is counting unacked messages in a remove-only data structure `dtree`. Each published message id is associated with a list of queues where it was routed to. On confirm of queue failures queues were removed from the list As soon as there are no queues in the list - the message can be confirmed. This meant that if all queues fail with "not abnormal" reasons - the message may be confirmed, but not enqueued. This change removes dtree data structure, replacing it with specific unconfirmed_messages data structure. It tracks queue pids similarly to dtree, but also has an API to record confirms and failures differently, keeping track of which queues received at least one confirm. If all pids fails or confirm, but not all queues received confirmation - it means not all queues enqueued the message and the message should be rejected This is different from the current behaviour, but corresponds to the docs and common sense. [#163952410]