| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
| |
This is only so we don't reach the log size limit on Travis CI.
|
| |
|
|
|
| |
This should help reduce the load in Travis CI or when doing quick
testing locally.
|
| |
|
|
| |
It should fix transient failures in CI.
|
| | |
|
| |\
| |
| | |
Update with Ra server supervision changes
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| | |
30 seconds seem too short currently in CI.
|
| |\ \
| | |
| | | |
Remove default bindings
|
| | | |
| | |
| | |
| | |
| | |
| | | |
This avoids duplicates after an existing installation is upgraded.
References #1721.
|
| | | |
| | |
| | |
| | |
| | | |
rabbit_binding:exists checks bindings table. Since default bindings
are not in that table anymore, it should check for queue existence.
|
| | | |
| | |
| | |
| | |
| | | |
Default bindings are not represented in the mnesia database but still
expected in the management UI and the rabbitmqctl command.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The min-masters locator was originally designed to count bindings,
but this was confusing for people wanting to distribute queues rather
than routes to queues. This was changed in 1d413eac80c2adb6844b82c8ce57e21a04a55b04
to count only queues which have at least one binding. But queues always
have bindings (default) and hence it's equivalent to listing queues.
Since default bindings are removed the location was broken. This commit
changes the location to actually list queues rather than bindings.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
Routing from default exchange is performed without querying bindings
and they cannot be unbound and only show in `rabbitmqctl list_bindings`.
There is no point in keeping them and they are slowing down cleanup.
|
| |\ \ \
| | | |
| | | | |
Introduce a configurable limit to message size
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
* Use smaller messages for tests
* No need to publish a message above the hard limit, use a helper (these are unit tests)
* Wording
|
| | | | | |
|
| | |\ \ \
| |/ / /
|/| | | |
|
| |\ \ \ \
| |_|/ /
|/| | | |
Honor cipher suite order in rabbitmq.conf
|
| | | | |
| | | |
| | | |
| | | | |
rabbitmq.conf. The ct helpers will not verify this as the snippets and results are deep sorted
|
| |/ / / |
|
| |\ \ \
| | |/
| |/| |
Quorum queue: purge should not remove checkout out messages.
|
| |/ /
| |
| |
| |
| |
| | |
As these may be returned by a consumer after the purge.
[#162811681]
|
| |\ \
| | |
| | | |
rabbit_fifo: apply/4 -> apply/3
|
| |/ /
| |
| |
| | |
Support the latest Ra api changes.
|
| | |
| |
| |
| |
| |
| | |
This can save us some reductions by avoiding ets read.
[#161983593]
|
| |/
|
|
|
|
|
|
|
|
|
| |
Add `max_message_size` configuration to configure limit
in bytes.
If message is bigger - channel exception will be thrown.
Default limit is 128MB.
There is still a hard limit of 521MB.
[#161983593]
|
| |\
| |
| | |
Do not include x-delivery-count header on first delivery.
|
| |/
|
|
| |
[#162755631]
|
| | |
|
| |\
| |
| | |
quorum queue: reset message bytes on purge
|
| |/
|
|
| |
[#161505138]
|
| |\
| |
| | |
Bugfixes
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When a consumer node is disconnected the quorum queue will return all
outstanding messages for the consumer to the queue as it cannot know if
the consumer will ever come back or not and cannot leave things checked
out forever. If the consumer node then reconnectes and the consumer
channel is still alive it may try to query for missing deliveries and
this previously crashed if the messages had been returned to the main
queue. This fix makes the query safer as well as handling missing
messages better.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
Fixes bug that muddled up the checkout order when a consumer is
cancelled with more than 32 messages checked out.
Dialyzer fixes.
[#162698673]
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
1. rabbit_quorum_queue:update_metrics/2 used calls to remote processes.
To avoid this blocking the ra server in a partition we now spawn a new
process for this.
2. Due to a refactoring miss commands over the soft limit where never
formatted successfully.
|
| |\ \
| |/
|/| |
Take "true" case into consideration
|
| | | |
|
| |/
|
|
|
|
| |
Fixes #1682
Call E() instead of crashing with badmatch, retry when queue is mirrored
|
| |\
| |
| | |
Report message bytes in quorum queue stats
|
| |/
|
|
| |
[#161505138]
|
| |\
| |
| | |
Implement consumer listing for quorum queues
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| | |
Refactor rabbit_fifo internal commands to use records instead of plain
tuples to provide a little bit more compile time safety and make it
easier to extend in the future.
[#162584074]
|
| |\ \
| |/
| | |
Ensure quorum queue consumers are cleaned up
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
Fixes a bug where the consumer_created metrics table wasn't cleared when
a consumer was cancelled.
Also removing some injected handlers from rabbit_fifo
[#162583758]
|
| |\ \
| | |
| | | |
Remove the unused truncate module
|
| | |/
| |
| |
| | |
This kind of truncation is done automatically by lager now.
|
| |\ \
| |/
|/| |
Roll wal on memory alarm
|