Alfonso, Thank you very much indeed.
-----Original Message-----
From: "Alfonso Espitia" <aespitia@castleworldwide.com>
To: <pound@apsis.ch>, "Dave Steinberg" <dave@redterror.net>
Date: Tue, 1 Apr 2008 07:42:16 -0500
Subject: RE: [Pound Mailing List] pounds - few questions - stickiness
After a user closes the browser, it depends on how you set your cookies
as to whether they're still there or not. I think the default is for
cookies to expire at the end of a session (maybe not), but you can set
cookies to expire on a certain date instead (like current_date+1). If
that's how you set your cookies, I would imagine that if they log back
in to your site, that they'd go back to the original server.
Just check on how your applications are setting the cookies expiration
time.
Also, I wouldn't recommend running a web server and the load balancer on
the same machine. I think it can be done if they're running on
different ports, but I still wouldn't recommend it...then again, I
haven't tried it. If you do try it, I would give the load
balancer/server a low priority since it's doing double duty.
--Alfonso
-----Original Message-----
From: Mariusz Szyszka [mailto:szycha@bydnet.com.pl]
Sent: Tuesday, April 01, 2008 2:01 AM
To: pound@apsis.ch; Dave Steinberg
Subject: Re: [Pound Mailing List] pounds - few questions - stickiness
Thanks guys for quick response.
I was not very precise in what I said before regarding sticky session.
Generally I assume that my Load Balancer )pound) will handle session
among a few application server.
Let's see an example. User A is redirected to App Server A. The session
is sticky because of cookies. User A closes the browser and logs back to
the server 10 minutes later. Will user A be connetced to tha same App
Server ?
Or rather will by handled to another one because the cookies has been
deleted or expired?. I would like avoid the situation where user is
AWLAYS redirected to the same App server when new session is
established. The goal is that subsequnts requestes within session goes
tro the same App server but each new session shall go to another one.
And second new item. Let's assume I have 4 application server in the
back end. Can I install the pound on one of them and serve the traffic
among those 4 servers?
Hopefully that makes my assuption clear.
regards
Mariusz
-----Original Message-----
From: Dave Steinberg <dave@redterror.net>
To: pound@apsis.ch
Date: Mon, 31 Mar 2008 17:56:31 -0400
Subject: Re: [Pound Mailing List] pounds - few questions - stickiness
> The requests within the session should be sticky to the same
> application
> server. It seems the pounds supports this feature ("Pound has the
> ability
to
> keep track of sessions between a client browser and a back-end
> server")
> It seems to me I can use cookies:
> Session
> Type Cookie
> ID "sess"
> TTL 300
> End
Right, right.
> However not sure If I understand it. Can you please flesh this
behaviour
out
> ? Who insert the cookies ? Pounds or back end application?
The backend / your application.
> Using a cookie approach does it mean that new session from the same
browser
> will be load balance among all back end servers? I thought
> if I use cookies always each session will go to the same back edn
server.
I believe you're correct, the same cookie will land you on the same
backend. That's of course the point of sticky sessions. :)
> How are back ends selected ? I mean how does the pound select back end
from
> a list of active. (round robin, random, by number connections?)
By priority, or if priorities are equal, I believe its random.
> Does pound collect any info (stats) such as active clients, active
> connections, etc in html format ...
poundctl can give you some info, but you'd have to convert to HTML
yourself.
> Where can I found more info than under
http://www.apsis.ch/pound/index_html
[ http://www.apsis.ch/pound/index_html]?
Take a look at the man page included with the source code. Its quite
complete.
Regards,
--
Dave Steinberg
http://www.geekisp.com/ [http://www.geekisp.com/]
http://www.steinbergcomputing.com/ [ http://www.steinbergcomputing.com/]
--
To unsubscribe send an email with subject unsubscribe to pound@apsis.ch.
Please contact roseg@apsis.ch for questions.
--
To unsubscribe send an email with subject unsubscribe to pound@apsis.ch.
Please contact roseg@apsis.ch for questions.
--
This message has been scanned for viruses and
dangerous content by SecureMail, and is
believed to be clean.
--
To unsubscribe send an email with subject unsubscribe to pound@apsis.ch.
Please contact roseg@apsis.ch for questions.