| Commit message (Collapse) | Author | Age | Files | Lines |
| | |
|
| |\
| |
| | |
Expose some message index related functions for salvage tool
|
| | |
| |
| |
| |
| | |
`rabbit_msg_store:scan_file_for_valid_messages/1`
`rabbit_queue_index:scan_queue_segments/4`
|
| |\ \
| | |
| | | |
Mark node as ready after it actually is
|
| | | | |
|
| | | |
| | |
| | |
| | | |
This fixes the concatenation of all jobs.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The function spec of `erl_epmd:port_please/3` was fixed in Erlang 23. we
can re-enable Dialyzer in this file.
This was mandatory anyway, otherwise disabling Dialyzer for this one
triggered the following warning in rabbit:do_run_postlaunch_phase/0:
rabbit.erl:1059: Function log_broker_started/1 will never be called
That's because the pattern matching we did on the return value of
`erl_epmd:port_please/{2,3}` was considered incorrect by Dialyzer,
causing a possible crash. The crash would happen before
`log_broker_started/1` would be called, which meant
`log_broker_started/1` would be dead code.
|
| |/ /
| |
| |
| |
| |
| |
| |
| | |
`rabbit_networking:boot()` and the maintenance mode preparation was
moved or added after we marked the node as ready. Therefore, functions
such as `rabbit:is_running()` were lying. This led to bugs such as
"rabbitmqctl wait" tu return too early, or testcases starting to run
before the node was started and thus failing.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
`maintenance_mode_status` feature flag
This is a prerequisite for the testsuites to work. The second benefit is
that if the feature flag is unavailable (say, in mixed-version testing),
the testcases will be skipped.
While here, remove all trailing whitespaces.
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| | |
it is timing-sensitive
|
| | |
| |
| |
| |
| |
| |
| |
| | |
* Use the latest 3.7.x release candidate during mixed-version testing
because no releases contain the latest fixes to the feature flags
helpers yet.
* Restore Elixir version to the oldest we support (also the compiler in
recent versions of Elixir fails frequently, at least in Concourse).
|
| | |
| |
| |
| |
| | |
This fixes the layout of the logged list and the style of the source
file.
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| |\ \
| | |
| | | |
Corrected a typo in man page of rabbitmqctl.8.
|
| |/ / |
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
and add a VMware copyright notice.
We did not mean to make this code Incompatible with Secondary Licenses
as defined in [1].
1. https://www.mozilla.org/en-US/MPL/2.0/FAQ/
|
| |\ \
| | |
| | | |
Catch case where feature flag is not enabled
|
| |/ /
| |
| |
| |
| |
| | |
Follow-up to #2349
Part of #2321
|
| |\ \
| | |
| | | |
Node drain (maintenance mode) operations
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Otherwise we'd lose mixed version cluster compatibility.
We cannot pre-create a table since it will be checked for existence
on cluster peers.
We cannot use an upgrade function since it assumes a cluster-wide
restart.
A feature flag avoids as many headaches as possible and when
flags are detected to be compatible on node start, they are
all enabled automatically.
References #2321.
|
| | | |
| | |
| | |
| | | |
Part of rabbitmq/rabbitmq-server#2321
|
| | | |
| | |
| | |
| | | |
Part of rabbitmq/rabbitmq-server#2321
|
| | | |
| | |
| | |
| | | |
Part of rabbitmq/rabbitmq-server#2321
|
| | | |
| | |
| | |
| | |
| | |
| | | |
maintenance mode
Part of rabbitmq/rabbitmq-server#2321
|
| | | |
| | |
| | |
| | | |
References #2321
|
| | | |
| | |
| | |
| | | |
References #2321
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | | |
Part of rabbitmq/rabbitmq-server#2312
Pair: @kjnilsson
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | | |
and restart them upon revival.
Part of rabbitmq/rabbitmq-server#2321
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This makes the refs predictable and easy to compute
from a listener record. Then suspending all listeners
becomes a lot simpler.
While at it, make protocol applications clean up
their listeners when they stop. This way tests
and other callers that have to stop the app
would not need to know anything about
its listeners.
Part of rabbitmq/rabbitmq-server#2321
|
| | | |
| | |
| | |
| | | |
Part of rabbitmq/rabbitmq#2321
|
| | | |
| | |
| | |
| | | |
Part of #2321.
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
For cases where no node is eligible we use the local node.
This should only be possible during a brief window of time
before a node that's been drained drops its connections.
However, be benign and optimistically let the queue operation
proceed.
Part of rabbitmq/rabbitmq-server#2321
|
| | | |
| | |
| | |
| | | |
Part of #2321.
|
| | | | |
|