| Commit message (Collapse) | Author | Age | Files | Lines |
| |\
| |
| |
| |
| | |
rabbitmq/restore-dist-port-configuration-for-windows-service
scripts/rabbitmq-service.bat: Configure Erlang distribution port
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
As said in the comment, this is normally done at runtime now (see
rabbitmq/rabbitmq-server#2180). However, we must configure the
distribution on the command line specifically for the Windows service.
Until this patch, the distribution was enabled with the correct
nodename, but the TCP port configuration was not set. This caused a
regression because the selected TCP port was random instead of the
expected default of 25672.
This patch restores the previous behavior.
Fixes rabbitmq/rabbitmq-server#2387.
|
| |/ |
|
| |\
| |
| | |
rabbit_prelaunch: Load configuration before Erlang dist. is started
|
| |/
|
|
|
|
|
|
| |
The reason is that kernel's `net_ticktime` can be configured in the
Cuttlefish or Erlang configuration files. If we start the distribution
first, then the configuration parameter is ignored.
Fixes #2377.
|
| |\
| |
| | |
Attempt to increase rabbit_fifo_int_SUITE stability
|
| | |
| |
| |
| |
| | |
Wait for messages to have been enqueued before proceeding with the body
of the test case
|
| |\ \
| | |
| | | |
Make connection_metric_idemp_test example rather than property based
|
| | |/
| |
| |
| |
| |
| |
| |
| | |
rather than a property based test.
The property test flakes occassionally, and without consistent input values.
Idempotency should be properly demonstrated with 2 or more attempts at the
action anyway.
|
| |\ \
| | |
| | | |
Stricter setup in the confirms_survive_* tests
|
| | |/
| |
| |
| | |
Wait until at least one message has been confirmed before triggering the survivable change
|
| | |
| |
| |
| | |
Things like staying in the 80-column limit and spaces around '='.
|
| | |
| |
| |
| | |
References #2368, #2373, rabbitmq/rabbitmq-management#818.
|
| | |
| |
| |
| |
| |
| | |
See #2368 comments for the background.
References #2368, #2373.
|
| |\ \
| |/
|/| |
Revert "Ensure rabbitmq_management is loaded"
|
| |/ |
|
| |
|
|
|
|
| |
for Erlang 23 compatibility of 'rabbitmq-diagnostics observer'
References zhongwencool/observer_cli#68.
|
| |\
| |
| | |
Support RABBITMQ_HOME paths containing brackets on windows
|
| |/
|
|
|
|
|
|
|
|
| |
If the environment variable RABBITMQ_HOME contained a path with either
'(' or ')' (for example, a path under C:\Program Files (x86)\), then
the script would unexpectedly exit with the error
'\some\path was unexpected at this time'. This was caused by the
parenthesis being interpreted as part of the batch 'if/else'.
Adding quotes around the arguments to the SET command fixes the problem.
|
| |\
| |
| | |
Ensure rabbitmq_management is loaded
|
| |/
|
|
|
|
|
|
|
|
|
| |
This ensures that `rabbitmq_management` settings are available at this point in time.
If the plugin is not available, this step is skipped because the application can not be loaded.
To test:
```
RABBITMQ_SERVER_ADDITIONAL_ERL_ARGS='-rabbitmq_management load_definitions "/tmp/defs.json"' ./sbin/rabbitmq-server
```
|
| |\
| |
| | |
Deprecate 'ctl node_health_check'
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* It requires a fully booted node, so not generally suitable for a Kubernetes readiness probe.
* It can produce false positives
* It is too intrusive and CPU-intensive to use at scale
* Most operators do not understand what it really does and when they learn about it,
consider it to be too opinionated and intrusive
Time for the One True Health Check™ to retire from duty.
Part of rabbitmq/rabbitmq-cli#426
|
| | |
| |
| |
| |
| |
| | |
Before this patch, we were using `rabbit_env` directly which computed
the environment again. In the end, we would compute the environment four
times instead of just once.
|
| |/
|
|
| |
It is already possible on Unix.
|
| |\
| |
| | |
Improves logging for user and permission-related management functions
|
| | |
| |
| |
| | |
Part of rabbitmq/rabbitmq-server#2363
|
| | |
| |
| |
| |
| |
| |
| | |
At debug level only since this code path is used by client connections
and authentication failures for are already visibly logged as errors.
Part of rabbitmq/rabbitmq-server#2363
|
| | |
| |
| |
| | |
Part of rabbitmq/rabbitmq-server#2363
|
| | |
| |
| |
| | |
Part of rabbitmq/rabbitmq-server#2363
|
| | |
| |
| |
| | |
Part of rabbitmq/rabbitmq-server#2363
|
| | |
| |
| |
| | |
Part of rabbitmq/rabbitmq-server#2363
|
| | | |
|
| | | |
|
| | |
| |
| |
| | |
Part of rabbitmq/rabbitmq-server#2363
|
| | |
| |
| |
| | |
Part of rabbitmq/rabbitmq-server#2363
|
| | |
| |
| |
| | |
Part of rabbitmq/rabbitmq-server#2363
|
| |\ \
| |/
|/| |
Stricter test setup for simple_ha_SUITE
|
| | |
| |
| |
| | |
Wait for an ack on the first message sent to the queue before proceeding with the test, since we assert on that message in the tail of the test.
|
| |\ \
| | |
| | | |
Use the newly defined MSG_STORE_WORKER_WAIT for rabbit_msg_store
|
| | | | |
|
| | | |
| | |
| | |
| | | |
Part of #2324.
|
| | |/
| |
| |
| | |
In order raise the default timeout for gracefully shutting down message stores, without affecting a larger set of supervisors, introduce a specific macro for this case
|
| | | |
|
| |\ \
| |/
|/| |
rabbit_mnesia:is_virgin_node/0: take overridden Ra data directory into account
|
| |/
|
|
|
|
|
| |
as well as the default location because it can exist for various reasons
early on node startup.
Part of rabbitmq/rabbitmq-server#2317
|
| |\
| |
| | |
Introduce raft.data_dir to new style configuration schema
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
As an experimental feature for now. To be sure that this value
has the desired effect we may have to tweak the way Ra dependency
is started.
Some ealy tests suggest this works as expected already.
Per discussion with @kjnilsson.
Closes #2354.
|