| Commit message (Collapse) | Author | Age | Files | Lines |
| |\ |
|
| | |\
| | |
| | | |
Improve `partitions_SUITE`
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The testcase simulates a partial partition which should be detected by
the two nodes on each side of the partition. They should both decide
there is a partial partition and stop.
However, sometimes one of the node is faster than the other one: it sees
the partial partition and stops before the second node even sees the
partition. When this happens, the second node doesn't even bother to
stop (because the partition is full now). Thus the testcase fails
because it expects both nodes to stop.
This patch tries to sync partial partition checks so both A and B
decide there is a partial partition.
[#146911969]
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The testcase simulates a small delay between the times B sees A down
and C sees A down too. Because A is effectively down for both, B's
rabbit_node_monitor shouldn't see a partial partition.
When B sees A down first, it asks C about A. In the scenario the
testcase simulates, C tries to contact A, fails and reports to B that A
is down.
However, because of the way we simulate that delay, sometimes, C still
sees A when B asks about it, because the link between A and C isn't
blocked yet. When this happens, B decides there is a partial partition.
Therefore, the testcase fails because it tests that this shouldn't
happen.
To try to be closer to a real-world situation (where A would be really
down for B and C), we suspend C's rabbit_node_monitor until we block the
link between A and C. Thus B still asks C about A, but C only processes
the request when the link is indeed down.
[#146911969]
|
| | |/ |
|
| | | |
|
| | | |
|
| | | |
|
| |\ \
| | |
| | | |
Locking support in cluster formation
|
| | |\ \ |
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Adapted from autocluster to avoid race conditions on startup
rabbitmq-server#125
[#146871615]
|
| |\ \ \ \
| |_|/ /
|/| | /
| | |/
| |/| |
|
| | |\ \
| | | |
| | | | |
OTP-20 compatibility workaround for queue directory names. 3.6 only!
|
| | | | | |
|
| | | |\ \
| | |/ /
| |/| | |
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
OTP-20 has different binary format for atoms (since OTP-14337)
So term_to_binary generates different value.
testm_to_binary_compat now have a function to generate a binary
identical to pre-20 versions.
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
rabbitmqctl wait will have more flexibility if the rabbitmqctl node
will do the waiting. For example when net_ticktime is lower than
startup time wait would not fail.
|
| | |_|/
|/| |
| | |
| | | |
common_test node
|
| |\ \ \
| |/ /
| | |
| | |
| | | |
Conflicts:
docs/rabbitmq.config.example
|
| | |\ \
| | | |
| | | | |
Improve documentation around new default for background garbage collection
|
| | |/ /
| | |
| | |
| | | |
background_gc_enabled to false to match the behavior of the Makefile.
|
| |\ \ \
| | | |
| | | | |
Remove stale comment
|
| |/ / / |
|
| |\ \ \
| | | |
| | | | |
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
|