ClusterIP is very similar to Microsofts Windows Load Balancing component, maybe Google can show you issues that others
had on that side to help you plan. I worked on that comp. at M$ a while ago (1999). ClusterIP may have the same issues
that WLBS had like:
All hosts see all traffic and must discard the ones that are "not mine". Increased network traffic.
Then there is the multicasting issue too, some switches had problems with this.
Also tune the hashmode based on the types of protocols you'll see, meaning
http as sourceip-sourceport-destport, and ssh as sourceip (or maybe sourceip-sourceport depending on traffic load).
Good luck.
/djb
Gary W. Smith wrote:
This should work but if you run into needing slightly more functionality than can be procuded by iptables you're stuck. This was our case. We decided on LinuxHA and then finally on LinuxHA/DRBD. This combination worked well for us (plus it was easy to configure). Our additional funcitionality is based on the fact that we need to NAT serveral IP's.
Hope this helps.
Gary Smith
