
Performance Tuning
50
To drop queues, use the zenqdelete script:
$ zenqdelete zenoss.queues.zep.rawevents
To get queue names, use rabbitmqctl:
$ rabbitmqctl list_queues -p /zenoss
6.7.1. Message Persistence
You can configure whether messages published to a given exchange:
• Exist only in memory (and are lost if Rabbit fails), or
• Are persisted to disk (and recoverable)
Non-persistent messages are much faster, and do not consume disk space if a queue backs up.
To change default message persistence, edit the value of the following line:
exchange.default.delivery_mode = Value
where possible values are:
• 1 - Do not persist to disk
• 2 - Persist to disk (the default value)
Examples
To prevent unprocessed events from being saved to disk before being processed by zeneventd, uncomment
the line:
# exchange.$RawZenEvents.delivery_mode = 1
To prevent processed events from being saved to disk before being de-duped and persisted by zeneventserver,
uncomment the line:
# exchange.$ZepZenEvents.delivery_mode = 1
To prevent heartbeats from being saved to disk before being handled by zeneventserver, uncomment the line:
# exchange.$Heartbeats.delivery_mode = 1
6.7.2. Message Compression
You can configure whether messages published to a given exchange should be compressed. To change default
message compression, edit the value of the following line:
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.
6.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
Kommentare zu diesen Handbüchern