max_messages actually corresponds to how many messages we try to send to the configured recipient before it moves onto the next queue in the list. Basically, it's super rudimentary QoS.
As for expiration, that's controlled by redis itself. Under the persistence configuration section, you can set a key called "entry_ttl" which takes a value in seconds. If you look in yagi/persistence/redis_driver.py you can see the default value specified at the top of the file. From: Craig Vyvial <cp16...@gmail.com<mailto:cp16...@gmail.com>> Date: Tue, 13 Mar 2012 13:50:19 -0500 To: openstack <openstack@lists.launchpad.net<mailto:openstack@lists.launchpad.net>> Subject: [Openstack] yagi caching messages for time I noticed that in the configuration file for yagi that there is no option for storing messages for a time period but rather a limit of max_messages. Does anyone know if there is a way to configure yagi to keep messages for a set amount of time? ###yagi/etc/yagi.conf### [consumer:notifications.warn] apps = yagi.handler.pubsubhubbub_handler.PubSubHubBubHandler, yagi.handler.redis_handler.RedisHandler exchange = nova exchange_type = topic routing_key = notifications.warn durable = False max_messages = 1000 -Craig Vyvial _______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net<mailto:openstack@lists.launchpad.net> Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
_______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
