| Commit message (Collapse) | Author | Age | Files | Lines |
| |\
| |
| | |
Switch to Mozilla Public License 2.0 (MPL 2.0)
|
| |/ |
|
| | |
|
| |\
| |
| | |
rabbit_prelaunch_early_logging: Configure `rabbit_log` as a Logger handler
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Currently, when the new Logger API exposed by Erlang is being used by an
application, messages are lost once Lager is configured. That is because
Lager does not know about Logger in this context.
To fix this, `rabbit_log` is configured as a Logger handler which calls
Lager API. This means that Logger messages are passed to Lager.
Logger's log level is to set to pass all messages (including debug).
Message routing/filtering is done by Lager instead.
This change depends on new log/2 function being added to the
`rabbit_log` module in rabbitmq-common.
|
| |\ \
| |/
|/| |
Attempt to further de-flake metrics/connection_metric_idemp_test
|
| |/
|
|
|
| |
Wait until the connection_metrics report the new connections, before
triggering the idempotent action under which they should stay stable.
|
| |
|
|
|
|
| |
This test still flakes occassionally even with the dynamic wait. The original
five second timeout might have been a bit short, as this test takes around 70-90
seconds when successful, so I'm bumping the timeout to 10s to see if it helps.
|
| | |
|
| |\
| |
| |
| |
| | |
rabbitmq/mk-resurrect-runtime-parameter-values-as-maps
Definition import: pre-format more values as maps where possible
|
| | |
| |
| |
| |
| | |
by avoiding distribution name/port conflicts that do resolve
themselves but only after a timeout.
|
| | |
| |
| |
| |
| |
| |
| | |
way HTTP API would
this makes them JSON serialisation-safe without any post-processing
of the returned data structure.
|
| |/
|
|
|
|
| |
Definition import should be able to cope with maps. We should move
away from using proplists to the extent practically possible, and
definition import is one area where we should be able to do that.
|
| | |
|
| |
|
|
| |
the value was changed in test, but not at its source
|
| |\
| |
| |
| |
| | |
rabbitmq/mk-check-if-node-is-mirror-sync-critical-should-ignore-exclusive-queues
Exclude exclusive queues from list_local_mirrored_classic_without_synchronised_mirrors
|
| | |
| |
| |
| |
| |
| | |
so that CLI tools don't have to do any post-processing.
References rabbitmq/rabbitmq-cli#432.
|
| | |
| |
| |
| |
| |
| |
| |
| | |
list_local_mirrored_classic_without_synchronised_mirrors
as they are not actually mirrored.
References rabbitmq/rabbitmq-cli#432.
|
| |\ \
| |/
|/| |
Add honeycomb integration for tests
|
| |/
|
|
|
|
|
|
| |
We treat the individual test case results as a kind of metric, and
collect those in the honeycomb.io observability tool. The intent is to
gain a better understanding of the suites from a statistical
perspective in order to gain greater insight into issues such as test
flakiness.
|
| |\
| |
| | |
Introduce a way to check if a node is the only cluster member
|
| | |
| |
| |
| |
| |
| |
| | |
A node with RabbitMQ stopped on it using `rabbitmqctl stop_app`
would report no running nodes even in a single node cluster.
References #2321
|
| | |
| |
| |
| |
| |
| | |
for CLI tools to output without any post-processing.
Part of rabbitmq/rabbitmq-cli#432
|
| |/
|
|
| |
Part of rabbitmq/rabbitmq-cli#432
|
| |\
| |
| | |
Restore CTL_ERL_ARGS env variables
|
| |/
|
|
| |
Fixes #2394
|
| |
|
|
| |
References #1627, #2276.
|
| |
|
|
|
|
|
|
| |
We have switched all doc guides to use "follower", "mirror" or "secondary"
years ago but some comments and test suites were never updated,
even though their changes would not be breaking.
This transition is a medium-term WIP.
|
| |
|
|
|
|
|
|
|
| |
We have switched all doc guides to use "mirror" or "secondary"
years ago but these were never updated.
Renaming functions and record/HTTP API fields (including CLI tools)
would be major a breaking change, so they will be aliased or renamed
with a lot more extensive review in the future.
|
| |
|
|
|
|
|
|
|
| |
We have switched all doc guides to use "mirror" or "secondary"
years ago but these were never updated.
Renaming functions and record/HTTP API fields (including CLI tools)
would be major a breaking change, so they will be aliased or renamed
with a lot more extensive review in the future.
|
| |
|
|
|
|
|
|
|
| |
We have switched all doc guides to use "mirror" or "secondary replica"
years ago but these were never updated.
Renaming functions and record/HTTP API fields (including CLI tools)
would be major a breaking change, so they will be aliased or renamed
with a lot more extensive review in the future.
|
| |\
| |
| | |
Import definitions in the post-launch phase
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
This is a behavior we use to provide because definitions were
imported before the empty DB boot step. Now when the definitions
are imported in the post-launch phase, we'd always end up with
default data seeded in addition to definitions being imported.
References #2384
|
| |/
|
|
|
|
|
| |
This way definitions that depend on a plugin, such as federation upstreams
or exchanges of custom types, can be imported successfully.
Closes #2384
|
| |\
| |
| | |
Makefile: Upgrade Cuttlefish from 2.2.0 to 2.3.0
|
| | |
| |
| |
| |
| | |
This fixes a crash of Cuttlefish when a line is made only of
whitespaces.
|
| |\ \
| |/
|/| |
drop deprecated HiPE compilation
|
| | |
| |
| |
| | |
Signed-off-by: Pierre Fenoll <pierrefenoll@gmail.com>
|
| | |
| |
| |
| | |
Signed-off-by: Pierre Fenoll <pierrefenoll@gmail.com>
|
| |/
|
| |
References #2389, #2387
|
| |\
| |
| |
| |
| | |
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
|