Greetings, I'm trying to get a good handle on queue sizing and memory usage. In a higher-traffic environment, I have a dedicated rsyslog machine with a large amount of ram. I want to try and find the right balance between large queues for burst traffic, but I also want to make sure that the queue sizes are small enough that we don't run out of memory and crash. I'm using 4.5.5 currently.
I'm currently using disk-backed memory queues, configured in fixedarray, like so: $MainMsgQueueSize 2000000 $MainMsgQueueMaxFileSize 50g $MainMsgQueueSaveOnShutdown on $MainMsgQueueHighWaterMark 15000000 $MainMsgQueueLowWaterMark 10000000 $MainMsgQueueType FixedArray $MainMsgQueueWorkerThreads 2 $ActionQueueSize 200000 $ActionQueueMaxFileSize 50g $ActionQueueSaveOnShutdown on $ActionQueueHighWaterMark 1500000 $ActionQueueLowWaterMark 1000000 $ActionQueueType FixedArray $ActionQueueWorkerThreads 1 I usually have upwards of a dozen action queue definitions, and my omfile outputs are based on hostname of the incoming connection. Is there some way I can calculate maximum memory use by the queuing system, or force the system to a set memory maximum where I -know- that it will simply start pushing back on the incoming connection instead of adding more data to the system? Thoughts? -Aaron _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com
