From 1ea3c0c586263f68e6da59a32d49c7322c0b5263 Mon Sep 17 00:00:00 2001 From: Michael Klishin Date: Fri, 15 Mar 2024 20:05:59 -0400 Subject: [PATCH] Document feature flags introduced in 3.13, closes #1842 --- docs/feature-flags.md | 46 +++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 46 insertions(+) diff --git a/docs/feature-flags.md b/docs/feature-flags.md index be8e1e9203..696fc5f32a 100644 --- a/docs/feature-flags.md +++ b/docs/feature-flags.md @@ -332,6 +332,52 @@ The following feature flags are provided by RabbitMQ core. Description + + + + khepri_db + +

+ Enables Khepri, a currently experimental schema data store + with vastly superior peer failure and network split handling characteristics + compared to Mnesia. +

+ +

+ Make sure to test Khepri extensively with appropriate workloads before using it in production. +

+ + + + + + 3.13.0 + message_containers + + Enables a new AMQP 1.0-based message format used internally. + + + + + + 3.13.0 + detailed_queues_endpoint + + Introduces the `GET /api/queues/detailed` HTTP API endpoint, + reduces the number of metrics served by `GET /api/queues/` + + + + + 3.13.0 + stream_update_config_command + + Removes `max_segment_size_bytes` from the list of policy keys that + can be dynamically updated for streams. Changing `max_segment_size_bytes` for an existing + cluster is not safe, so it is not a good fit for dynamic policy-based updates. + + + 3.12.0