| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |\
| |
| | |
Improve documentation around new default for background garbage collection
|
| |/
|
|
| |
background_gc_enabled to false to match the behavior of the Makefile.
|
| | |
|
| |\ |
|
| | |\ |
|
| | |/
| |
| |
| |
| | |
rabbitmq-server#1233
[#146160779]
|
| | |
| |
| |
| |
| | |
Already joined node message.
Changing disk node to disk should not fail
|
| | |
| |
| |
| |
| |
| | |
... even if the node is already a member.
This fixes a failure in the `join_and_part_cluster` testcase.
|
| | |
| |
| |
| |
| |
| |
| | |
The list of backends that will be available when 3.7.0 ships
is shaping up.
Still to port: etcd and Kubernetes.
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| | |
This name is both more descriptive and helps us avoid any possible
conflicts with rabbitmq-autocluster, in particular in the new config
format (Cuttlefish) that we will introduce for both soon.
Per discussion with @dcorbacho.
|
| |\ \
| |/ |
|
| | | |
|
| |\ \ |
|
| | | | |
|
| |\ \ \
| |/ /
|/| /
| |/ |
|
| | | |
|
| | | |
|
| |\ \
| |/ |
|
| | |\
| | |
| | | |
Update sup_delayed_restart_SUITE for rabbitmq-common#202
|
| | |/
| |
| |
| | |
To accommodate changes made in rabbitmq/rabbitmq-common#201.
|
| |\ \
| | |
| | | |
Configure MNESIA_BASE and MNESIA_DIR on dev environment
|
| | | |
| | |
| | |
| | |
| | | |
rabbitmq-server#1221
[#145264225]
|
| |\ \ \
| | | |
| | | | |
Update sup_delayed_restart_SUITE for rabbitmq/rabbitmq-common#201
|
| |/ / /
| | |
| | |
| | | |
To accommodate changes made in rabbitmq/rabbitmq-common#201.
|
| |\ \ \
| |/ /
|/| /
| |/ |
|
| | |\
| | |
| | | |
Don't expand plugins that are already unpacked
|
| | | | |
|
| | |\ \
| | | |
| | | | |
Introduce a new config parameter, total_memory_available_override_value, to override total amount of memory available to the node
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
memory
rabbitmq-server#1224
[#145450413]
|
| |\ \ \ \
| |/ / /
| | | |
| | | |
| | | |
| | | |
| | | | |
Conflicts:
src/file_handle_cache.erl
src/file_handle_cache_stats.erl
src/rabbit_runtime_parameters.erl
|
| | | | |
| | | |
| | | |
| | | | |
rabbit_misc:json_encode can return a list or a binary.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This module is generic enough and is used by the Erlang client. Moving
it is the last step to resolve the interdependency between the Erlang
client and the broker: with this change, the client only depends on
rabbitmq-common!
[#118490793]
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
Erlang 20.x warns if `export_all` is set in a module by default. We need
to turn the warning off.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Those are the functions to clear the read buffer cache in various
internal RabbitMQ processes. file_handle_cache still reads the
`fhc_read_buffering` and `fhc_write_buffering` rabbit application
variables, though.
Thus, this change almost removes a dependency of file_handle_cache on
the broker. Reading the configuration variable is acceptable for now so
this will allow us to move file_handle_cache to rabbitmq-common.
[#118490793]
|
| | |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The function is renamed to get_memory_use/1 in the process, to match
other functions in the vm_memory_monitor module.
The file_handle_cache uses that function. By moving it to
vm_memory_monitor, we remove a dependency of file_handle_cache on a
rabbit_* module. This will allow us to move both file_handle_cache and
vm_memory_monitor to rabbitmq-common and help remove a dependency in the
Erlang client on the broker because the former calls
file_handle_cache:obtain/0.
To sum up the situation before this commit with a graph:
amqp_network_connection --[depends on]--> file_handle_cache
(amqp_client) (rabbit)
file_handle_cache --[depends on]--> rabbit_memory_monitor
(rabbit) (rabbit)
And the situation we want to reach after the move:
amqp_network_connection --[depends on]--> file_handle_cache
(amqp_client) (rabbit_common)
file_handle_cache --[depends on]--> vm_memory_monitor
(rabbit_common) (rabbit_common)
rabbit_memory_monitor --[depends on]--> vm_memory_monitor
(rabbit) (rabbit_common)
[#118490793]
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | | |
~p will enclose node name (an atom) in single quotes, which our message
already has
|
| | | |
| | |
| | |
| | |
| | |
| | | |
Runtime parameters list functions do not accept info items
as arguments. To return correct number and items order in the new CLI
parameters should be sorted by info items order.
|
| | | | |
|
| |\ \ \ |
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | | |
This is a 'master' counterpart for #1226
|
| | |\ \ \
|/ / / /
| | | _ |
|
| | |/
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This prevents creating unnecessary files when running in embedded
mode, and in development mode it keeps code path clean and compatible
with different interactive tools.
Also some new error conditions are properly handled and logged:
- Failure to unpack an .ez-file
- Missing .app file in plugin directory
|
| |\ \
| |/ |
|
| | |
| |
| |
| |
| |
| | |
See the corresponding commit in rabbitmq-common for an explanation.
[#144697185]
|
| | | |
|
| |\ \
| | |
| | | |
Revert "Use new supervisor2:prep_stop to stop rabbit dependencies on shutdown"
|
