| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
| |
GUIDs are generated and announced when rabbit app starts.
In some cases, that takes minutes (many queues/bindings).
During that time, we can get false positives and declare
pause_minority because the Erlang VM responds but the GUID
has not been updated. By using and checking erlang:system_info(creation)
we get a unique value immediately after Erlang VM restart so we
can tell whether the node was restarted.
|
| |
|
|\
| |
| | |
Prometheus plugin: fix TLS port handling
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
All ssl options were stored in the same proplist, and the code was
then trying to determine whether an option actually belongs to ranch
ssl options or not.
Some keys landed in the wrong place, like it did happen in #2975 -
different ports were mentioned in listener config (default at
top-level, and non-default in `ssl_opts`). Then `ranch` and
`rabbitmq_web_dispatch` were treating this differently.
This change just moves all ranch ssl opts into proper place using
schema, removing any need for guessing in code.
The only downside is that advanced config compatibility is broken.
|
|\ \
| | |
| | | |
Handling of `stream_not_found` return value when init a stream client
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This error probably shouldn't happen if the system is correct, however
`stream_not_found` is a valid return value for the functions called
- it comes from `register_listener`.
Not handling it causes a case_clause (and long stacktrace) that is sent
to the client as an internal error, instead of a known protocol error.
Seen while debugging another issue.
|
|\ \ \
| | | |
| | | | |
Fix persistent message count display in mgmt UI
|
| | |/
| |/|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Fixes #3396
As can be seen in
https://github.com/rabbitmq/rabbitmq-server/blob/9cf18e83f279408e20430b55428a2b19156c90d7/deps/rabbitmq_management/priv/www/js/tmpl/queue.ejs#L171
there should be 3 colums for a classic queue.
While it's possible to share the same field with the quorum queues
case, I did it this way so that conditions for the labels and for the
values will have the same shape.
|
| | |
| | |
| | |
| | |
| | | |
Not worth testing in this mode, as the stream plugin
does not start without the stream_queue feature flag.
|
| | |
| | |
| | |
| | |
| | | |
For mixed version mode, where feature flags are
not explictely enabled.
|
| | |
| | |
| | |
| | |
| | | |
For mixed version mode, where feature flags are
not explictely enabled.
|
|/ / |
|
|\ \ |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
|\ \ \
| | | |
| | | | |
Finalize 3.9.8 release notes
|
| |/ / |
|
|/ / |
|
|\ \
| | |
| | | |
Declare stream with node down fix
|
| | |
| | |
| | |
| | |
| | |
| | | |
Deriving a max-cluster-size only from running nodes would create situations where
in a three-node with only two nodes running cluster it would select an non-running
node as follower.
|
| | | |
|
| | | |
|
| | | |
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
rabbitmq/dependabot/github_actions/actions/checkout-2.3.5
Bump actions/checkout from 2.3.4 to 2.3.5
|
|/ / /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Bumps [actions/checkout](https://github.com/actions/checkout) from 2.3.4 to 2.3.5.
- [Release notes](https://github.com/actions/checkout/releases)
- [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md)
- [Commits](https://github.com/actions/checkout/compare/v2.3.4...v2.3.5)
---
updated-dependencies:
- dependency-name: actions/checkout
dependency-type: direct:production
update-type: version-update:semver-patch
...
Signed-off-by: dependabot[bot] <support@github.com>
|
|\ \ \
| | | |
| | | | |
Fix stream coordinator log message
|
| |/ / |
|
| | |
| | |
| | |
| | |
| | |
| | | |
Fix an Erlang monitor leak when queue churn is high
(cherry picked from commit a78b76afcda60820cf78f16a509b50b8ec32789b)
|
|\ \ \
| | | |
| | | | |
Log response body of failed AWS requests
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | | |
Disable the stream_plugin if stream feature flag is not enabled
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
is not enabled.
fixes https://github.com/rabbitmq/rabbitmq-server/issues/3557
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
is not enabled.
fixes https://github.com/rabbitmq/rabbitmq-server/issues/3557
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Not to ctl.
References #3503
|
|\ \ \ \ \
| | | | | |
| | | | | | |
Add functions to create/delete super stream in manager
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
max-age, leader-locator, etc.
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | |/ / /
| |/| | | |
|
|\ \ \ \ \
| | | | | |
| | | | | | |
Adopt otp 24.1.2 for OCI workflow
|
| | | | | | |
|
|\ \ \ \ \ \
| |_|_|_|_|/
|/| | | | | |
Fix memory_breakdown for connection procs
|
|/ / / / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Instead of trying to read the ranch_server ETS table directly,
use an internal Ranch function that does the same. While neither
are documented, the latter is less likely to change.
|