david at lang
Feb 22, 2012, 5:01 PM
Post #2 of 2
(205 views)
Permalink
|
On Wed, 22 Feb 2012, Lu, Victor wrote:
> Hi,
>
> Any idea why the tcp communication from rsyslog client to rsyslog
> collector is persistent? I found for each selector rule it will have one
> connection to the collector. The collector will have too many TCP
> connections to handle. It will be a problem for large scale deployment.
>
> Is there any way to configure so that the TCP connections will not be persistent?
>
> Thanks in advance
This is normal behavior to avoid the overhead of establishing the
connections for each message.
Why are you thinking that this is a problem? it should be simple enough to
allow tens of thousands of connections to a single machine. The ulimit on
your OS may default to something much lower, but that should be an easy
thing to change.
Yes, each connection eats a little memory, but compared to the overhead of
processing the logs from that many machines, it should be trivial.
I don't believe that there is any way to have it not keep the connection
open.
David Lang
_______________________________________________
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com/professional-services/
|
