I believe I read this somewhere previously, but cannot currently find it. For a Disk Assisted In-Memory queue configuration, messages are pulled off the top of the disk queue, correct? So for a sufficiently busy action queue, messages will be dequeued out of order and delivered to their destination out of order?
When a disk assisted queue is being drained, current messages are delivered first, and then when the queue size drops 'low enough', rsyslog will pull messages from disk and send them.
So yes, the messages will be delivered out of order. This is only one of the many ways that messages can end up being processed out of order. Rsyslog is multi-threaded, so if you get busy enough to have two threads sending messages, they will each be processing messages independently of each other and this will result in re-ordering of messages. But even with traditional syslog, UDP packets have been known to get re-ordered over the network, causing logs to arrive out of order. The advanced features of Rsyslog can trigger this in more common cases, but it's a matter of how common this is, not if it happens or not.
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.
