rabbitmq-server/deps/rabbitmq_ct_helpers
Jean-Sébastien Pédron f973932a2d
quorum_queue_SUITE: Use Khepri fence before checking number of replicas
[Why]
When `wait_for_messages_ready/3` returns, we are sure that the replicas
are in the expected state. However, the `#amqqueue{}` record is updated
in Khepri, we don't know when all Khepri store members will be
up-to-date.

It can happen that `Server0` is not up-to-date when we query that record
to get the list of replicass, leading to a test failure.

[How]
First, the check is moved to its own function is `queue_utils`.

Then, if Khepri is being used, we use a Khepri fence to ensure previous
operations were applied on the given server. This way, we get a
consistent view of the `#amqqueue{}` record and thus the list of
replicas.
2025-07-30 15:04:47 +02:00
..
include Respect message_interceptors.incoming.set_header_timestamp 2024-04-10 11:40:49 +02:00
src quorum_queue_SUITE: Use Khepri fence before checking number of replicas 2025-07-30 15:04:47 +02:00
test Bump (c) line year 2025-01-01 17:54:10 -05:00
tools Verify non-zero DNS and email SAN 2024-10-29 16:41:20 +01:00
.gitignore Cleanup .gitignore files for the monorepo 2024-06-28 12:00:52 +02:00
CODE_OF_CONDUCT.md
CONTRIBUTING.md
LICENSE Replace @rabbitmq.com addresses with rabbitmq-core@groups.vmware.com 2023-06-20 15:40:13 +04:00
LICENSE-APACHE2 More missed license header updates #9969 2024-02-05 12:26:25 -05:00
LICENSE-MPL-RabbitMQ
Makefile Use Erlang.mk's native Elixir support for CLI 2025-03-18 10:02:49 +01:00