On Tue, 9 Sep 2014, Muhammad Asif wrote:
Hi Guys!
I need some understanding regarding Rsyslog queues.
1- Is it default behaviour of rsyslog to create a queue for any action.
Which force us to make it "Dierect Queue" for writing in local files.
Please elaborate following parameter in simple words.
1- *queue.timeoutenqueue (*default 2000 sec , 0 means indefinite)
2- *queue.checkpointinterval numbe*
* 3- queue.lightdelaymark* *number*
technically there is a queue between anything in rsyslog that generates modifies
or moves data and the workers that act on that data.
But the default is a "direct queue", which means no queue, a direct synchronous
communication between the pieces.
The exception to this is the "main queue"
All data from input modules is placed on the main queue for workers to pick up
and process per the rules. The workers execute the output module code to write
to files, send over the network, etc.
In a simple configuration, you can consider this the only queue in rsyslog.
take a look at
http://www.rsyslog.com/doc/master/rainerscript/queue_parameters.html
timeoutenqueue, if the message takes more than this amount of time to insert
into a queue, drop it as an error
checkpointinterval, if you are using a disk queue, every X messages rsyslog will
write housekeeping info to disk. data written between these checkpoints can be
lost in the case of a crash of rsyslog
lightdelaymark, if you have more than this number of messages in the queue,
inputs that are reliable will slow down how fast they accept new data.
David Lang
_______________________________________________
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com/professional-services/
What's up with rsyslog? Follow https://twitter.com/rgerhards
NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of
sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE
THAT.
