[rsyslog-notify] Forum Thread: Re: rsyslog: does rsyslog support in-oder log messages deliv - (Mode 'edit_last_post')

[noreply at adiscon.com]

User: IgorS 
Forumlink: http://kb.monitorware.com/viewtopic.php?p=27206#p27206

Message: 
----------
What about receiving order, does same principles apply?

For example, i have rsyslog installed on my machine with default
configuration. Only one output to file is created.

If from another machine i do the following:
cat <path_to_file_1GB> | nc <rsyslog host> 514
Or, i just create a TCP socket (in python for example,one thread only),
connect to (rsyslog_host, 514), read the 1GB file and send line-by-line.

I see that syslog save all messages to destination file, no message is lost
but order is mixed. 

If from the same machine where rsyslog is installed i execute:
cat <path_to_file_1GB> | nc <localhost host> 514

then messages are ordered.

This behavior is reproducable and i'm wondering what is the issue here. TCP
should guarantee order as well, right?

I'm aware of all refactoring that was done (<!-- m --><a class="postlink"
href="http://www.gerhards.net/download/LinuxKongress2010rsyslog.pdf">http://www.gerhards.net/download/LinuxK
... syslog.pdf</a><!-- m -->) but what confused me was this line from this
post (<!-- m --><a class="postlink"
href="http://blog.gerhards.net/2013/06/rsyslog-performance-main-and-action.html">http://blog.gerhards.net/2013/06/rsyslo
... ction.html</a><!-- m -->)

By default, both queues are set to one worker maximum. [b:1jvmrzyo]The
reason is that this is sufficient for many systems and it can not lead to
message reordering[/b:1jvmrzyo]. If multiple workers are concurrently
active, messages will obviously be reordered, as the order now, among
others, depends on thread scheduling order.

Is post outdated or i'm confused, there is a good chance  latter is true
since i don't have a lot of experience with rsyslog :)

Is there any way to configure rsyslog to preserve message order that it
receives? 

Igor.