On Tue, 8 Dec 2009, Ryan Lynch wrote:

> In the doc example, the server "primary-syslog.example.com" is always
> tried first, unless it's down, followed by
> "secondary-1-syslog.example.com", and then finally
> "secondary-2-syslog.example.com" only if both of the others are down.
> Here's the doc in question, BTW:
>
> * http://wiki.rsyslog.com/index.php/FailoverSyslogServer
>
> 1.  Is it possible to configure Rsyslog to pick randomly from a list
> of remote syslog destinations instead of following the listed order?
> If I have a large population of log generating hosts, I'd like to be
> able to distribute the total load amongst two or more "central" log
> receivers, with failover if a receiver dies. Assuming that we have a
> sound random-selection implementation, and a large enough population
> of hosts generating approximately equal amounts of log data, I should
> get an approximately even distribution across my receiver hosts. In
> the event that a receiver dies, its clients would randomly try another
> receiver, keeping the load close to even. Is this possible, with the
> existing failover mechanism?

this sort of thing is possible today, without using round-robin DNS

on linux there is an iptables option called CLUSTERIP that lets you create 
a single IP address on multiple machines, and each machine processes a 
portion of the traffic (based on a hash of one or more of dest port, dest 
IP, source port, source IP)

heartbeat (http://linux-ha.org) will manage a cluster of machines, 
including ones sharing an IP address like this.

if you have many systems sending to one central server they will be spread 
roughly evenly across the servers. if this is not even enough for you, 
version 5 has an option to close and re-open connections to the server 
every X messages, and since doing so changes the source port of the 
connection, this will spread the connections around the cluster more 
evenly.


David Lang
_______________________________________________
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com

Reply via email to