| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
| |
User, tags and hashed password can be inserted/updated at once,
increasing the performance of the storage backend - both for mnesia
and khepri.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
`khepri:find/2` expects a path and condition. We may want to
pre-populate the condition in the future, but for now - at least it
works.
|
| |
|
|
|
| |
In particular which node is picked while trying to make the Khepri
cluster match the Mnesia one.
|
| |
|
|
| |
... when a Mnesia-based node joins a Khepri-based node.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
... and not other EUnit macros.
Otherwise, this adds a dependency on EUnit. Also, `eunit.hrl` defines
`TEST` which might defeat some `-ifdef(TEST)` we may use.
|
| |
|
|
|
|
|
| |
This allows the migration function do perform some cleanup after the
running code switched to the new thing.
While here, fix a couple style issues in `rabbit_core_ff`.
|
| |
|
|
|
|
| |
This makes the behavior consistent with the virgin node startup
behavior. It also avoids users to be surprised with experimental
features being enabled.
|
| |
|
|
|
|
|
| |
Before this change, all feature flags were enabled by default when a new
node was started. Now, only the stable ones are enabled, not the
experimental ones. In other words, experimental feature flags must be
enabled explicitely.
|
| |\
| |
| | |
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
|
| | | | |
|
| | | | |
|
| | | | |
|
| |/ /
| |
| |
| |
| | |
These can make sense in some scenarios, e.g. when vhost/exchanges are
+created using self-service automation
|
| | | |
|
| |\ \
| | |
| | | |
Use a pattern to filter out some queues from global stats
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | | |
Uses same exclusion pattern as the management agent
|
| | | |
| | |
| | |
| | |
| | |
| | | |
Avoids multiple calls to `application:get_env` which can be very expensive.
Also limits filter to vhost_msg_stats, as queue_msg_stats are required for
individual queue metrics
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
Some plugins might create internal queues that should not be accounted
for the total number of messages on the system. These can now be filtered
out using a regular expression on the queue name. Individual queue stats
are still available
|
| |\ \ \
| | | |
| | | | |
Add systemd hardening parameters in rabbitmq-server.service.example
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
systemd offers various options to harden services. To see details please
visit https://en.opensuse.org/openSUSE:Security_Features#Systemd_hardening_effort
|
