openstack/oslo.messaging
Code Issues Proposed changes

[doc] Better document rabbit_transient_queues_ttl option

Browse Source 
With implementation of rabbit_stream_fanout option,
rabbit_transient_queues_ttl is now used to control the size of stream
as well.
While it made sense to re-use the option, it is behaving quite
differently from what is currently described as now it controls not the
queue TTL itself, but messages TTL inside the queue, which is good to
be explicit about.

Change-Id: I78c5066d5d62192f2206893c04823b83791ebdc3
This commit is contained in:
Dmitriy Rabotyagov 2024-09-04 11:26:11 +02:00
parent d601f7aae0
commit 7dea32bc4c
1 changed files with 8 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
oslo_messaging/_drivers/impl_rabbit.py
View File

@ -217,7 +217,14 @@ rabbit_opts = [
'0 as value will disable the x-expires. If doing so, '
'make sure you have a rabbitmq policy to delete the '
'queues or you deployment will create an infinite number '
'of queue over time.'),
'of queue over time.'
'In case rabbit_stream_fanout is set to True, this option '
'will control data retention policy (x-max-age) for '
'messages in the fanout queue rather then the queue '
'duration itself. So the oldest data in the stream queue '
'will be discarded from it once reaching TTL '
'Setting to 0 will disable x-max-age for stream which '
'make stream grow indefinitely filling up the diskspace'),
cfg.IntOpt('rabbit_qos_prefetch_count',
default=0,
help='Specifies the number of messages to prefetch. Setting to '