
Performance tuning
39
exchange.default.compression = Value
where possible values are:
• deflate - Use DEFLATE algorithm
• none - Do not compress messages
By default, all messages published to all exchanges are compressed.
5.7.3. Message TTL
You can configure the time-to-live value (TTL) of messages published to a queue, setting them to expire if they have
not been delivered to a client within a given time.
To change default message TTL, edit the following line:
queue.default.x-message-ttl = Value
where Value is a value in milliseconds. By default, messages expire after one day (86400000 milliseconds).
Examples
To cause unprocessed events to expire if they have not been processed within one hour (for example, if zeneventd
backs up in an event storm), uncomment the line:
# queue.$RawZenEvents.x-message-ttl = 3600000
To cause processed events to expire if they have not been persisted within one hour (for example, if zeneventd backs
up in an event storm), uncomment the line:
queue.$ZepZenEvents.x-message-ttl = 3600000
5.7.4. Queue expiration
You can configure unused queues to be deleted automatically after a period of time. "Unused" means that the queue
has no consumers, and has not been re-declared.
To change default queue expiration, edit the following line:
queue.default.x-expires = Value
where Value is a value in milliseconds. By default, queues expire after one day (86400000 seconds).
5.8. Configuring the heartbeat monitor
The heartbeat monitor allows daemons that have connections to RabbitMQ to set up heartbeats with the message
broker, and is part of Zenoss Service Dynamics Global Operations Management. Configuration options allow you to
specify how often the message broker should expect to receive heartbeats from the consumers created by the daemon.
If three intervals pass without the message broker receiving a heartbeat, the broker will disconnect the consumer.
You may want to configure the interval if you are fine-tuning a high availability environment and encountering issues
with consumers not disconnecting quickly enough from RabbitMQ when a failover scenario occurs.
By default, a heartbeat is sent every 60 seconds. You can modify this default in two ways:
• Modify the value of the amqpheartbeat setting (by default, 60), in the $ZENHOME/etc/zengomd.conf file.
Comentarios a estos manuales