|
Hello,
On Tue, 1 May 2001, Joseph Mack wrote:
> Peter Mueller wrote:
> >
> > Modify the below lines in httpd.conf and restart httpd. I believe there's a
> > 'persistence=seconds' flag in LVS that you can set that should correspond to
> > what you put in httpd.conf?
>
> I played with all of this when I first was trying to figure out what was
> going on.
> I expected that if the connection was persistent, then all hits would be
> downloaded
> in the same connection and there would be only one ActConn in the ipvsadm
> table.
> There wasn't. I think I got a pile of InActConns spread between the
> real-servers.
>
> I've just upgraded to apache_1.3.19 as my old apache didn't survive the
> upgrade
> to glibc-2.2.2.
>
> I now see several ActConn spread around the real-servers. If these are
> (netscape)
> persistent connections, then I would expect them to be reused if I did a
> reload,
> but the number of Act Conn increases by the same number each reload
> (ipvs-1.0.7-2.2.19).
> while netstat -an | grep 80 on the real-servers shows the connections going
> from
> FIN_WAIT to LISTEN. The client shows 4 connections in CLOSE_WAIT while the
> director
> has 12 ActConns.
>
> (Julian is this right?)
>
> If a client with persistent http connects through an LVS to real-servers with
> httpds
> which can maintain a persistent httpd connection and the client asks for a
> web page
> full of gifs, then I expect the html page will be first downloaded (opening a
> persistent
> connection to the real-server). The client will then issue several commands
> of the type
> "GET /foo.gif"
>
> If these requests go over the established connection, then the ActConn
> counter on ipvsadm
> won't change (will stay at 1).
Hm, I think the browsers fetch the objects by creating 3-4
connections (not sure how many exactly). If there is a KeepAlive option
in the httpd.conf you can expect small number of inactive connections
after the page download is completed. Without this option the client is
forced to create new connections after each object is downloaded and
the HTTP connections are not reused.
> However this doesn't happen. The counters go up as seen by ipvsadm. Each gif
> must
> be requested through a new connection.
The browsers reuse the connection but there are more than one
connections.
> so I still don't understand what's going on
>
> Any ideas anyone?
>
> Joe
> --
> Joseph Mack PhD, Senior Systems Engineer, Lockheed Martin
> contractor to the National Environmental Supercomputer Center,
> mailto:mack.joseph@xxxxxxx ph# 919-541-0007, RTP, NC, USA
Regards
--
Julian Anastasov <ja@xxxxxx>
|
