From: David Busby <busby@edoceo.com>
Cc: netfilter@lists.netfilter.org
Subject: Re: Clusterip usage
Date: Mon, 13 Jun 2005 14:48:12 -0700 [thread overview]
Message-ID: <42ADFF1C.2020503@edoceo.com> (raw)
In-Reply-To: <57F9959B46E0FA4D8BA88AEDFBE582909E99@pxtbenexd01.pxt.primeexalia.com>
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
>
next prev parent reply other threads:[~2005-06-13 21:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-13 16:48 Clusterip usage Gary W. Smith
2005-06-13 21:48 ` David Busby [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-06-13 12:07 Gavin Henry
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=42ADFF1C.2020503@edoceo.com \
--to=busby@edoceo.com \
--cc=netfilter@lists.netfilter.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox