Article delegate-en/802 of [1-5169] on the server localhost:119
  upper oldest olders older1 this newer1 newers latest
[Top/Up] [oldest] - [Older+chunk] - [Newer+chunk] - [newest + Check]
Newsgroups: mail-lists.delegate-en

[DeleGate-En] Re: how to set up delegate as a load balancing web server
22 May 2000 09:04:11 GMT (Yutaka Sato)

On 05/16/00(10:43) you "CIOS/Comserve Support Staff" <> wrote
in <_A794@delegate-en.ML_>
 |    In our situation we have three physical machines running OS/2, each
 |with its own IP address: (,
 |(, (
 |    Our web server is on ( but it's topping out
 |on some of the functions it performs (too many hits at once) and we'd
 |like to spread out the load across one or both of our other two
 |machines, which are mostly idle.  However, this needs to be transparent
 |to the remote user of our web services (e.g., they always contact
 |"" even though they might reach the web server at port 289
 |    Do you have any sense for how to set this up in delegate?

As long as I know, the simplest way to do it is setting your DNS
server to return the multiple IP addresses of hosts of your
alternative HTTP servers for the query on "".  But I
don't know a usual way to realize a single virtual server merging
multiple servers running on port numbers different from each other.

With DeleGate, you can do it in several ways although every HTTP
communication must be relayed by a DeleGate server at the
representative machine ("" in your case).
I myself have never tried this but I think the following will do.

1) static MOUNT

  delegated \
            SERVER=http \
            MOUNT="/**" \

  -- only* is served by the second server

2) round-robin HOSTS

  delegated \
            SERVER=http://servers:289 \
            HOSTS="servers/{,}" \

  -- port number of servers must be the same (289 in this case)

3) conditional MOUNT

  delegated \
            SERVER=http \
            MOUNT="/** from=[0-255].*.*.[0-127]" \
            MOUNT="/** from=[0-255].*.*.[128-255]"

  -- a server is selected based on the IP-address of the client

4) ICP

  Only if your HTTP server supports ICP... (it is not likely)


  Only if your HTTP server is DeleGate... (it is not likely)

I think the approach 3) can be recommendable, and I feel introducing
random selection of alternative equivalent MOUNTs can be useful.

Yutaka Sato <>   @ @ 
Computer Science Division, Electrotechnical Laboratory      ( - )
1-1-4 Umezono, Tsukuba, Ibaraki, 305-8568 Japan            _<   >_

  admin search upper oldest olders older1 this newer1 newers latest
[Top/Up] [oldest] - [Older+chunk] - [Newer+chunk] - [newest + Check]