| Commit message (Collapse) | Author | Age | Files | Lines |
| |\
| |
| | |
'check' function for health check of virtual hosts
|
| | |
| |
| |
| | |
[#163451547]
|
| |\ \
| | |
| | | |
Add an option to dead-letter rejected publishes
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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 `reject-publish-dlx` overflow strategy, which is similar to
`reject-publish` strategy, but also dead-letters rejected messages.
Closes #1443
|
| | |
| |
| |
| |
| |
| | |
Add process messages to the error message.
Try harder to kill queues.
|
| | |
| |
| |
| |
| | |
This is to prevent false-positives on slow systems and detect genuine
errors better.
|
| |\ \
| | |
| | | |
Improve quorum_status command
|
| | | |
| | |
| | |
| | | |
Make it compatible with the pretty table formatter.
|
| | | | |
|
| | | | |
|
| | | | |
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
rabbitmq/fix-notify-limiter-after-consumer-timeout-change
Adapt clause in notify_limiter to consumer timeout changes
|
| |/ / / |
|
| | | | |
|
| | | | |
|
| | | | |
|
| |\ \ \
| | | |
| | | | |
Make sure that publishes to dead or unaccessible queues return nack
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| |/ / /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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]
|
| |\ \ \
| |_|/
|/| | |
Move check for active readers to message store GC action function
|
| | | | |
|
| | | | |
|
| | | | |
|
| | |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Message store GC postpones processing of file, which have readers.
When performing an action, it asserts that there are no readers.
Check for readers may race with readers update by a queue, crashing
the message store.
Make check and assert work with the same lookup to reduce failure rate.
In case of races the queue process should handle exception instead.
Addresses #2000
[#165755203]
|
| |\ \
| |/
|/| |
Fix type issues with send_drained message
|
| |/
|
|
|
|
| |
For quorum queues.
[#165796741]
|
| | |
|
| |
|
|
|
|
|
|
| |
Hiding the export behind the `TEST` macro should work on the paper.
Unfortunately, when we compile a test plugin as part of the
`feature_flags_SUITE` testsuite, `rabbit` is recompiled without the
`TEST` macro. This causes the testsuite to fail with an `undef`
exception because initialize_registry/1 is not exported anymore.
|
| |\
| |
| | |
Always close channel on consumer timeout
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| | |
In order to keep things simple and consistent this changes consumer
timeouts to always close the channel instead of cancelling and
returning.
|
| | |
| |
| |
| |
| |
| |
| |
| | |
validate_strategy/1 error value is `{error, FormatString, Args}`, not
the usual `{error, Reason}`.
This incorrect pattern matching was found thanks to the
`set_policy_command_test.exs` testsuite in rabbitmq-cli.
|
| |\ \
| | |
| | | |
Policy validation must return 'ok' or an error
|
| | | | |
|
| | | |
| | |
| | |
| | | |
[#165689664]
|
| | |/
| |
| |
| |
| |
| | |
Any other value will break the validation cycle and leave the rest
of the arguments without validate
[#165689664]
|
| |/
|
|
|
| |
This will ease the backport to 3.7.x where that feature flag does not
exist.
|
| | |
|
| | |
|
| |
|
|
| |
[#164931055]
|
| |\
| |
| | |
QQ SAC: process all consumers on noconnection
|
| |/
|
|
|
|
|
|
| |
There can be multiple single active consumers in the consumers map if
all but one are cancelled. Take this into account when processing
noconnections.
[#165438843]
|
| |\
| |
| | |
Reset overflow queue property to drop-head if policy is unset.
|