My config looks like your original one, except that the session stuff
was after the "backend" directive, instead of before.  I doubt that will
make a difference, but maybe someone else knows.

--Alfonso

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Cam
Roberts
Sent: Tuesday, September 30, 2008 5:15 PM
To: [email protected]
Subject: Re: [Pound Mailing List] load is not balanced when session
handling

Thanks for the response,  The site is actually live so the traffic is
coming in from all over the place.

I was thinking along the same lines and actually ignored the lopsided
effect during my testing for exactly this reason, I assumed since all
the load was coming from a handful of test servers I wasn't seeing
realistic production behaviour.  However the problem continued after we
went "live" with it.

Thanks,
 --Cam Roberts

On Tue, Sep 30, 2008 at 4:55 PM, Alfonso Espitia <
[EMAIL PROTECTED]> wrote:

> Are you trying this from a different location?
>
> If you try to hit it from the same location, it will direct you to the

> same server (because you ARE coming from the same IP).
>
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Cam
> Roberts
> Sent: Tuesday, September 30, 2008 4:06 PM
> To: [email protected]
> Subject: [Pound Mailing List] load is not balanced when session
> handling
>
> Hi,
>   I've configured pound with two BackEnds and Session Type IP, TTL
300.
>
> However all the load goes to one of the back end servers, I never see
> an apache connection on the other until the "primary" goes down.  I'm
> not using Emergency, and if I comment out the Session block the load
> is balanced evenly between the two servers.
>
>
> Relevant portion of my pound.cfg:
>
>        Service
>                BackEnd
>                        Address 10.0.0.2
>                        Port    80
>                End
>                Session
>                        Type IP
>                        TTL 300
>                End
>        End
>        Service
>                BackEnd
>                        Address 10.0.0.4
>                        Port    80
>                End
>                Session
>                        Type IP
>                        TTL 300
>                End
>        End
>
>
> Originally I had:
>
>        Service
>                Session
>                        Type IP
>                        TTL 300
>                End
>                BackEnd
>                        Address 10.0.0.2
>                        Port    80
>                End
>                BackEnd
>                        Address 10.0.0.4
>                        Port    80
>                End
>        End
>
> The behaviour seems to be identical with both of the above
> configurations, it doesn't do any load balancing when Session is
> declared.
>
> From my understanding of the manpage load should still be balanced
> when session handling is used, individual users will be bound to a
> single server but it should alternate with each new connection.  Am I
> misunderstanding session handling?
>
> --
> Thanks,
> --Cameron Roberts
>
>
> --
> To unsubscribe send an email with subject unsubscribe to
[EMAIL PROTECTED]
> Please contact [EMAIL PROTECTED] 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
[EMAIL PROTECTED]
> Please contact [EMAIL PROTECTED] for questions.
>


--
To unsubscribe send an email with subject unsubscribe to [EMAIL PROTECTED]
Please contact [EMAIL PROTECTED] 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 [EMAIL PROTECTED]
Please contact [EMAIL PROTECTED] for questions.

Reply via email to