| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
| |
This is a manual rebase of rabbitmq-common #349
https://github.com/rabbitmq/rabbitmq-common/pull/349/commits/1c09c0f824cf2eca9284035db3f079465edb5733
|
| |\
| |
| | |
Add compress option for file rotation
|
| | |
| |
| |
| |
| |
| | |
Related to #3835
https://www.erlang.org/doc/man/logger_std_h.html
|
| |\ \
| | |
| | | |
Extend log.file.rotation.date parser
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Note that Lager itself doesn't handle certain combinations:
* $W0H45 is fine
* $W0D1H45 fails with an error
but hopefully what we have now should be enough for
a minimalistic built-in log rotation feature.
|
| | | |
| | |
| | |
| | |
| | |
| | | |
to successfully parse all cases presented in Lager docs.
References #3831
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
rabbitmq/rabbitmq-server-3841-stream-consumer-nested-record
Create configuration nested record in stream consumer record
|
| | | | |
| | | |
| | | |
| | | | |
References #3841
|
| | | |/
| |/|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Only a couple of fields of the stream consumer record change
very frequently (credits and Osiris log reference), so this commit
introduces a nested record in the main consumer record that
contains the immutable fields. This potentially avoids producing
a lot of garbage, especially when the consumer state contains
several properties (consumer name, or single active consumer information
in the future).
Fixes #3841
|
| |\ \ \
| |/ /
|/| |
| | |
| | | |
rabbitmq/rabbitmq-server-3783-response-code-for-undefined-stored-offset
Return "no offset" (19) code when stored offset is undefined
|
| | | |
| | |
| | |
| | | |
Fixes #3783
|
| | |/
|/| |
|
| | | |
|
| |\ \
| | |
| | | |
Match help box to correct item
|
| |/ /
| |
| | |
before it was right after Auto expire
|
| |\ \
| | |
| | | |
Initial 3.9.11 release notes
|
| |/ / |
|
| |\ \
| |/
|/| |
Remove flaky assertion
|
| |/
|
|
| |
Thanks @kjnilsson
|
| |\
| |
| | |
QQ: remove decoded properties before storing messages
|
| | |
| |
| | |
Very small spelling change
|
| | |
| |
| |
| |
| |
| | |
We're also typically storing the encoded properties as well.
We only really need one. e.g. an enqueue command with a 2 byte payload
serialises to 290 bytes compared to 463. A nice saving.
|
| |\ \
| | |
| | | |
Query total number of messages on stream leader on queue.declare
|
| | | | |
|
| | | | |
|
| |\ \ \
| | | |
| | | | |
Introduce a new CLI tool (scope), rabbitmq-tanzu (backport #3815)
|
| |/ / /
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
For Tanzu (commercial) plugins to attach their commands to instead of
polluting rabbitmqctl.
Pair: @pjk25
(cherry picked from commit 6e0f2436faf86c0233af8b75125f9754a33fec77)
|
| |\ \ \
| |/ /
|/| | |
To deactivate limit of all QPids when the limiter has been changed from 'limit' to 'unlimit'.
|
| | |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
'limit' to 'unlimit'.
Otherwise, the QPids will still to ask limiter whether it can be sent before delivering.
This will degrade performance, especially when the limiter and QPid are on different nodes.
When 'can_send' is deactivated, the test results are as follows:
id: test-100147-150, time: 400.016s, sent: 17654 msg/s, returned: 0 msg/s, confirmed: 17658 msg/s, nacked: 0 msg/s, received: 17663 msg/s, min/median/75th/95th/99th consumer latency: 1775/5899/6486/7369/8440 μs, confirm latency: 2171/5581/6127/7026/7911 μs
test stopped (Reached time limit)
id: test-100147-150, sending rate avg: 17630 msg/s
id: test-100147-150, receiving rate avg: 17630 msg/s
When limiter and QPid are on the same node and 'can_send' is activated, the test results are as follows:
id: test-095229-474, time: 400.015s, sent: 13246 msg/s, returned: 0 msg/s, confirmed: 13247 msg/s, nacked: 0 msg/s, received: 13245 msg/s, min/median/75th/95th/99th consumer latency: 3777/7316/8345/10447/11392 μs, confirm latency: 4074/7308/8257/10336/11341 μs
test stopped (Reached time limit)
id: test-095229-474, sending rate avg: 13317 msg/s
id: test-095229-474, receiving rate avg: 13317 msg/s
we have seen, for the message rate, the test showed a 24% drop.
|
| |\ \
| | |
| | | |
tcp_listener: avoid logging listener arguments on shutdown
|
| | | | |
|
| | | |
| | |
| | |
| | | |
Per suggestions from @lhoguin
|
| | | | |
|
| | | |
| | |
| | |
| | | |
Closes #3803
|
| | | |
| | |
| | |
| | |
| | |
| | | |
If you are using bazel, you can switch to this with:
1. `bazelisk build //tools:erlang_ls.config`
2. `cp bazel-bin/tools/erlang_ls.config erlang_ls.config`
|
| |\ \ \
| |_|/
|/| | |
Adopt latest bazel-erlang
|
| |/ /
| |
| |
| | |
- bazel-erlang@050faedb2a3422a60d6b98678c714ed1a61ec71d
|
| |/
|
|
|
|
|
|
| |
Before this commit, the tests were not including any settle, return, or
discard Ra commands.
Do not pattern match against 'ra_event' because nowadays:
_Opts = [local, ra_event]
|
| |\
| |
| | |
To stop collect_statistics when rabbitmq_management_agent has been disabled
|
| | |
| |
| | |
After stopping the 'rabbitmq_management', these statistics tables are still being refreshed.
|
| |\ \
| |/
|/| |
Fix case where quorum queue consumer is cancelled while message is about to be delivered
|
| | | |
|
| | | |
|
| | |
| |
| |
| | |
Fixes #3729
|
| |\ \
| | |
| | | |
Link to most recent description of Osiris chunk format
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The most recent description of Osiris chunk format does not reference
the timestamp field to be "posix-ish" anymore. This was bit misleading
as it is Erlang's system time.
Add link to Erlang system time documentation to the subscription command
description to avoid confusion about the timestamp field.
|
| |\ \ \
| |_|/
|/| | |
Add optional metrics for vhost and exchange count
|
| | | | |
|
