| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
| |
Alternative for #1388 that does not use process dictionary.
Requires rabbitmq/rabbitmq-common#228
Fix waiting_bump values
|
| |\
| |
| | |
Report strategy, erlang total, rss and allocated memory
|
| | |
| |
| |
| | |
[#152311595]
|
| | |
| |
| |
| | |
[#152311595]
|
| |\ \ |
|
| | |\ \
| | | |
| | | |
| | | |
| | | | |
rabbitmq/mk-dont-throw-when-connection-pid-is-non-local
Make rabbit_networking:close_connection/2 more benign
|
| | |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The function relies on a fanout to all running cluster nodes
which in turn check their local connection process group.
All errors that might arise are ignored.
There are at least two scenarios where the current behavior makes
little sense:
* A connection process has just terminated (but is still present in the stats DB)
* A node could not respond (or respond in time) to the fanout
In both cases claiming that connection pid is "not a connection pid"
is misleading and likely will leave the user puzzled. This change
makes connection_close/2 more benign: it simply logs a warning and returns
instead of throwing.
There are only two call sites that use it: rabbitmqctl and an HTTP API
handler, so the chances of non-connection pids passed in are pretty slim.
Per discussion with @gerhard.
|
| |\ \ \
| |/ / |
|
| | |\ \
| | | |
| | | | |
Accept strings and atoms for queue_master_locator setting
|
| | |/ /
| | |
| | |
| | | |
Fixes #1411
|
| | |/
|/| |
|
| |\ \
| |/ |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Previously the value was limited to 1 due to a bug in Ranch 1.0:
it didn't depend on the ssl app, which means Ranch/ssl shut down order
was not guaranteed. This led to scary but entirely harmless exception traces
in the log, one per TLS acceptor.
The issue is no longer present in Ranch 1.3.x and 1.4.0.
Per discussion with @essen.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
Nodes fail to start and log that a node with such name is already running.
The rest of the test is functional, however.
This is a workaround to get the pipeline going, it could be that the
VM does not terminate in some cases we expect in this long test. In certain
parts I don't see why it would.
|
| |\ \
| | |
| | | |
Configurable default consumer prefetch for new channels
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | | |
rabbitmq-server#1367
[#151216783]
|
| |\ \ \
| | |/
| |/| |
|
| | | | |
|
| | |\ \
| | | |
| | | | |
Start `rabbit` application as temporary in tests.
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
Some tests output can break when `rabbit` application failure
stops the node. Make it possible to configure restart type.
|
| | |\ \ \
| | | | |
| | | | | |
Re-introduce consumer bias & set to 2.0
|
| | | | | |
| | | | |
| | | | |
| | | | | |
[#152235655]
|
| | |/ / /
| | | |
| | | |
| | | | |
This reverts commit 155eb6b0bffe3126ab18ab228296821ce0dc1f8c.
|
| |\ \ \ \
| |/ / /
| | | /
| |_|/
|/| | |
Conflicts:
src/rabbit_vm.erl
|
| | |\ \
| | |/
| |/| |
Add more sections to the memory breakdown.
|
| | | |
| | |
| | |
| | |
| | |
| | | |
If a node memory is measured using `allocator` or `rss`
strategies, we can calculate unused memory and report it
separately in the memory breakdown.
|
| |\ \ \
| |/ /
| | |
| | |
| | |
| | | |
Conflicts:
src/rabbit_channel.erl
src/rabbit_control_main.erl
|
| | |\ \
| | | |
| | | | |
Performance enhancements
|
| | | | |
| | | |
| | | |
| | | | |
[#152240490]
|
| | | |/
| | |
| | |
| | | |
[#152240490]
|
| | |\ \
| | |/
| |/| |
Handle errors returned via RPC during shutdown
|
| | | | |
|
| | | | |
|
| | | | |
|
| | |/
| |
| |
| |
| |
| | |
Added an exit() statement to trigger an error and then some case statements to handle it.
QA of commit 51aca8851eba66445ad5b164fc92b2ffa0692fc2
|
| |\ \
| |/ |
|
| | |\
| | |
| | | |
Flush messages to disk in batches.
|
| | | |\ |
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
If messages should be embedded to a queue index, there will
be no credit flow limit, so message batches can be too big
and block the queue process.
Limiting the batch size allows consumer to make progress while
publishers are blocked by the paging-out process.
[#151614048]
|
| | | | | |
|
| |\ \ \ \
| |/ / / |
|
| | |\ \ \ |
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | | |
We already have rabbit.channel_max, frame_max.
|
| | | |\ \ \
| |/ / / /
| | | | |
| | | | | |
https://github.com/cloudamqp/rabbitmq-server into cloudamqp-max_connections
|
| | | | | | |
|
| | | |/ / |
|