Phil Pennock wrote:
The "easy" fix is theoretically to configure up extra private addresses as aliases on the backend, and distribute the load over all of them. This avoids having multiple ports and multiple entries -- it's one cyrus.conf listening. The problem may be making sure that the front-end knows that several backends are tied together as being one real system, to avoid interesting failover effects.
Why not have the extra IPs on the front-end? ---- Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
