From edd8fbcb5b51a2aff1a6111247c5e8f73f0609a6 Mon Sep 17 00:00:00 2001 From: Michael Klishin Date: Tue, 10 Sep 2024 23:03:31 -0400 Subject: [PATCH] 4.0.0-rc.1 release notes: cosmetics --- release-notes/4.0.0.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/release-notes/4.0.0.md b/release-notes/4.0.0.md index e82052752870..717be122bac8 100644 --- a/release-notes/4.0.0.md +++ b/release-notes/4.0.0.md @@ -1,6 +1,6 @@ ## RabbitMQ 4.0.0-rc.1 -RabbitMQ `4.0.0-rc.1` is a preview of a new major release. +RabbitMQ `4.0.0-rc.1` is a candidate of a new major release. Starting June 1st, 2024, community support for this series will only be provided to [regularly contributing users](https://github.com/rabbitmq/rabbitmq-server/blob/main/COMMUNITY_SUPPORT.md) and those who hold a valid [commercial support license](https://tanzu.vmware.com/rabbitmq/oss). @@ -50,7 +50,7 @@ Messages that are redelivered 20 times or more will be [dead-lettered](https://w This limit is necessary to protect nodes from consumers that run into infinite fail-requeue-fail-requeue loops. Such consumers can drive a node out of disk space by making a quorum queue Raft log grow forever without allowing compaction -of older entries. +of older entries to happen. If 20 deliveries per message is a common scenario for a queue, a dead-lettering target or a higher limit must be configured for such queues. The recommended way of doing that is via a [policy](https://www.rabbitmq.com/docs/parameters#policies).