| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
| |
As they are not able to run.
|
| |\
| |
| | |
Increase aten poll interval
|
| |/
|
|
|
|
|
|
|
| |
A longer interval will reduce the likely hood that unnecessary leader
elections are triggered in quorum queues due to transient network
issues. This increases it from the default of 1s to 5s which increases
the time it takes to detect genuine network partitions somewhat. Ra still uses
monitors so connection failures will not have to wait this additional
time.
|
| |
|
|
| |
For mixed versions.
|
| |\
| |
| | |
Revert unintentional assertion
|
| |/
|
|
|
|
| |
PR #1818 introduced an unintended assertion here. Previously the record
was updated with the new queue pid. With the change, it became an
assertion.
|
| |\
| |
| | |
reject-publish strategy support for quorum queues
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| | |
As the current default is way to large for queues that never empty but
only keep a small backlog.
|
| | |
| |
| |
| |
| |
| | |
The quorum queue will track the timestamp of whenever a consumer was removed and
periodically check if the queue should be deleted based on it's expiry
configuration.
|
| | |
| |
| |
| |
| | |
To allow for future extensions without necessitating a machine version
upgrade
|
| | |
| |
| |
| |
| | |
As depending on which is the current leader this may or may not be
returned.
|
| | | |
|
| | |
| |
| |
| | |
To v0 version which has an additional field.
|
| | | |
|
| | |
| |
| |
| | |
when the rabbit_fifo:version/0 function is missing.
|
| | | |
|
| | | |
|
| | |
| |
| |
| | |
Growing shrinking does not necessarily work in mixed versions.
|
| | |
| |
| |
| | |
As this works better with mixed Ra machine versions
|
| | |
| |
| |
| | |
that cannot pass due to Ra machine versioning restrictions.
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| | |
QQs cannot be declared in two node clusters with different machine
versions. This setup should be an anomaly so changing some suites to
better represent sensible conigurations. This should also allow some
mixed-versions tests to pass.
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The reject publish overflow strategy for quorum queues is an inexact
implementation that relies on the cooperation of publishing channels.
When a channel first wants to publish to a quorum queue it first issues
a synchonous register_enqueuer command which will return the current
queue overflow state as reject_publish if the queue is full.
The queue will also notify any active enqueuers when it reaches the
limit but will continue to accept any enqueues it receives after that.
Once the queue size goes below 80% of the limit(s) the queue will again
notify enqueuers that they can resume publishin inte the queue.
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| | |
Also rename v0 state back to rabbit_fifo else it could never work with
old state!
|
| | |
| |
| |
| | |
This results in a lower memory use per message.
|
| | |
| |
| |
| |
| | |
First commit in a series that will evolve the rabbit_fifo state machine
into version 1.
|
| | |
| |
| |
| | |
for VESC-984
|
| |\ \
| |/
|/| |
Support recently introduced Ra WAL settings in rabbitmq.conf
|
| |/ |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
Concourse has recently had a high rate of false positives
at clustering stage. The suite still finishes
in a very reasonable amount of time.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
rabbit_connection_tracking:clear_tracked_connection_tables_for_this_node/0
... instead of
rabbit_connection_tracking:clear_all_connection_tracking_tables/0. They
latter calls the former and the former exists in all release branches.
This fixes the undef exception when running the testsuite with
mixed-versions clusters.
While here use rabbit_ct_broker_helpers:rpc_all() instead of having a
loop to call rabbit_ct_broker_helpers:rpc().
|
| |\
| |
| |
| |
| |
| |
| | |
Conflicts:
src/rabbit_channel.erl
src/rabbit_direct.erl
src/rabbit_networking.erl
|
| | |
| |
| |
| | |
This reverts commit e86fa81a3f90599d03b2f9beaaa56cfb6a4226f1.
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| | |
to reduce sporadic failures.
|
| | |
| |
| |
| |
| | |
Killing a local connection process makes the test flaky.
For the purpose of this suite, a clean close is good enough.
|
| | | |
|