From: Drew Leske <dleske@uvic.ca>
To: pablo@blueoakdb.com
Cc: netfilter@lists.netfilter.org
Subject: Re: Login load balancing
Date: Wed, 26 Apr 2006 11:40:10 -0700 [thread overview]
Message-ID: <444FBE8A.7080803@uvic.ca> (raw)
In-Reply-To: <017e01c6695e$1e77d550$0419a8c0@fly>
Hi Pablo,
Pablo Sanchez wrote:
>> The only half-solution I have come up with so far is to define a 'director'
>> box with the 'bob' alias, and then periodically grab load metrics from the
>> participating hosts, determine of the 'bob's which is the least loaded, and
>> then *cough* update a DNAT rule to redirect requests coming in for 'bob' to
>> the least-loaded 'bobX'.
>
> I believe the above is what you'll want to implement. As your research has
> probably already shown, the load balancers in the market are for HTTP. A
> good load balancer will need to communicate with the backend clients so it
> has data on load and other metrics necessary for it to make a decision on
> which server to serve.
You're right about load-balancing HTTP. Everybody and their dog wants to
load-balance HTTP for some reason. ;) But my dog insists on load-balancing SSH.
I have also found something called LVS, but as I've mentioned in another
post this is unsuitable for us. Grabbing the load data as I've said is no
problem--the default SNMP daemon provides CPU load I believe by default, and
it's no problem at all to provide for additional information. This part is
trivial since I've already implemented SNMP elsewhere.
> You could use wget to fetch metrics from all the servers (include a
> timestamp so you know when your data is stale) and have the director
> consider this information when it punches down new IPTABLEs rules.
SNMP would be faster and more lightweight I believe; wget implies I'd have
either an HTTP or FTP service running on each of those machines. Plus,
these connections would be subject to TCP timeouts, so if one of the
machines is down, my metric-gathering script would take forever timing out
on it. SNMP fails a lot faster. Also, there'd be quite a bit less parsing
to do of the results.
Thanks for your response!
Drew.
--
Drew Leske :: Systems Group/Unix, Computing Services, University of Victoria
dleske@uvic.ca / +1250 472 5055 (office) / +1250 588 4311 (cel)
next prev parent reply other threads:[~2006-04-26 18:40 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-26 17:33 Login load balancing Drew Leske
2006-04-26 18:03 ` Mailings'AT'netzwerk.cc
2006-04-28 10:36 ` Daniel Ivanov
2006-04-28 16:54 ` Drew Leske
2006-04-26 18:20 ` Pablo Sanchez
2006-04-26 18:40 ` Drew Leske [this message]
[not found] ` <1146073387.24375.74.camel@sehe-c4.berlin.teles.de>
2006-04-26 18:27 ` Drew Leske
2006-04-27 10:16 ` Arnt Karlsen
2006-04-27 17:34 ` Drew Leske
2006-04-28 10:00 ` Arnt Karlsen
2006-04-28 16:37 ` Drew Leske
2006-04-28 18:23 ` Arnt Karlsen
2006-04-28 18:36 ` Drew Leske
2006-04-30 9:51 ` Arnt Karlsen
2006-04-26 21:37 ` Carl-Daniel Hailfinger
2006-04-26 21:56 ` Drew Leske
2006-04-27 10:31 ` michael
2006-04-27 17:37 ` Drew Leske
2006-04-27 17:42 ` Drew Leske
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=444FBE8A.7080803@uvic.ca \
--to=dleske@uvic.ca \
--cc=netfilter@lists.netfilter.org \
--cc=pablo@blueoakdb.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.