Return-Path: Delivered-To: apmail-httpd-users-archive@www.apache.org Received: (qmail 43320 invoked from network); 30 Mar 2011 00:08:28 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 30 Mar 2011 00:08:28 -0000 Received: (qmail 90320 invoked by uid 500); 30 Mar 2011 00:08:25 -0000 Delivered-To: apmail-httpd-users-archive@httpd.apache.org Received: (qmail 90180 invoked by uid 500); 30 Mar 2011 00:08:25 -0000 Mailing-List: contact users-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: users@httpd.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list users@httpd.apache.org Received: (qmail 90172 invoked by uid 99); 30 Mar 2011 00:08:25 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 30 Mar 2011 00:08:25 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of icicimov@gmail.com designates 209.85.216.45 as permitted sender) Received: from [209.85.216.45] (HELO mail-qw0-f45.google.com) (209.85.216.45) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 30 Mar 2011 00:08:20 +0000 Received: by qwj8 with SMTP id 8so733881qwj.18 for ; Tue, 29 Mar 2011 17:07:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=gaWYPDloeXVdXY8YRKcSddsQ5MTZ1EgLg/cG534aQ4E=; b=ijEg0L41C9o5k6TtkorRUq35XBqWZmRY5T866oO1DeCAUYd1Ybuj6+fpWEn2NAcpLl lAnJs4vr5+FIFEbuU3CBTUjAeKTkO2HR4Tn1CHo1CnV5vR1cpkZsCcbCyMCSrxv58CK4 sXjFkzOePN+QrWHqjHzQaMpQVVBtXQ+0AQjeY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=dpFYFHLivBny5Uk+6pbrLmBlVs/26Zxgd5jn4SfNtFJ2CSYxVRluC04TDYmxJBOuF6 oU3mqKQzooUAwpuRDISAUQAl6W0di/yPB+GqKnaTgdbMZID1xadJFuI86pPBLbv2yC6Z xsmMYB1+SRFbKPyH31wF1zjBpfxnPTkZ7lB7o= MIME-Version: 1.0 Received: by 10.229.241.198 with SMTP id lf6mr448240qcb.198.1301443679055; Tue, 29 Mar 2011 17:07:59 -0700 (PDT) Received: by 10.229.85.1 with HTTP; Tue, 29 Mar 2011 17:07:58 -0700 (PDT) In-Reply-To: References: Date: Wed, 30 Mar 2011 11:07:58 +1100 Message-ID: From: Igor Cicimov To: users@httpd.apache.org Content-Type: multipart/alternative; boundary=0016362844ac2feca3049fa7f80a Subject: Re: [users@httpd] Active Active Data center and stickyness --0016362844ac2feca3049fa7f80a Content-Type: text/plain; charset=ISO-8859-1 Also the difference between GTM and LTM is that GTM enables fail-over between geographically different sites and for LTM that is possible only for local sites. Nothing to do with the persistence feature. On Wed, Mar 30, 2011 at 10:59 AM, Igor Cicimov wrote: > Strange because a quick search gives me this > > > http://devcentral-sea.f5.com/Community/GroupDetails/tabid/1082223/asg/50/aft/26947/showtab/groupforums/Default.aspx > > > On Wed, Mar 30, 2011 at 10:17 AM, Mohit Anchlia wrote: > >> Are you referrring to GTM or LTM. I have looked into it and even >> talked to F5 but currently they don't have this functionality for >> Prod. >> >> On Tue, Mar 29, 2011 at 4:16 PM, Igor Cicimov wrote: >> > Hi guys, >> > >> > Just scanned through the thread quickly so not sure if this makes any >> sense >> > but what about F5 source IP stickiness? >> > >> > Cheers, >> > Igor >> > >> > On Wed, Mar 30, 2011 at 3:34 AM, Mohit Anchlia >> > wrote: >> >> >> >> Currently, the load balancer don't provide the user >> >> stickyness/persistence for 'x' amount of time. At this point only >> >> option I see is that of creating a custom solution. It looks like >> >> there is no good solution. >> >> >> >> Problem here is User can be directed to any site by load balancer in >> >> active active scenario where load is being balanced as 1:1 ratio. >> >> >> >> Cookie was a good option but doesn;t work for non-browser client where >> >> browser connection to server A and then server A then make Http >> >> request. So in essence it's the ip of server A that is making the >> >> request and there is no way to use cookies in such scenarios. >> >> >> >> On Tue, Mar 29, 2011 at 7:25 AM, Ben Timby wrote: >> >> > On Mon, Mar 28, 2011 at 10:42 PM, Mohit Anchlia < >> mohitanchlia@gmail.com> >> >> > wrote: >> >> >> Thanks! We are using F5 GTM as global load balancer with LTM. So >> >> >> global load balancing is not a problem. Problem is user stickyness >> >> >> that need to persist beyond individual session. >> >> >> >> >> >> I forgot to mention that the problem is that these connections come >> >> >> from the servers using http rather than browser and that's why >> cookies >> >> >> here will probably not work. >> >> > >> >> > Then you will have to review your load balancer docs and see what >> >> > options are available and go from there. A common load balancing >> >> > method is SOURCE, where the source of the request is hashed to >> >> > determine the backend server to direct the request to. This would >> >> > ensure the same source always hits the same backend (as long as it is >> >> > available). The downside to this method is that upstream proxies hide >> >> > the client's IP address and undermine the load balancing >> effectiveness >> >> > of this method. However, you know the user (or group of users) will >> be >> >> > sticky. >> >> > >> >> >> >> --------------------------------------------------------------------- >> >> The official User-To-User support forum of the Apache HTTP Server >> Project. >> >> See for more info. >> >> To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org >> >> " from the digest: users-digest-unsubscribe@httpd.apache.org >> >> For additional commands, e-mail: users-help@httpd.apache.org >> >> >> > >> > >> >> --------------------------------------------------------------------- >> The official User-To-User support forum of the Apache HTTP Server Project. >> See for more info. >> To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org >> " from the digest: users-digest-unsubscribe@httpd.apache.org >> For additional commands, e-mail: users-help@httpd.apache.org >> >> > --0016362844ac2feca3049fa7f80a Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Also the difference between GTM and LTM is that GTM enables fail-over betwe= en geographically different sites and for LTM that is possible only for loc= al sites. Nothing to do with the persistence feature.

On Wed, Mar 30, 2011 at 10:59 AM, Igor Cicimov <icicimov@gmail.com> wrote:
Strange because a quick search gives me this

http://devcentral-sea.f5.co= m/Community/GroupDetails/tabid/1082223/asg/50/aft/26947/showtab/groupforums= /Default.aspx


On Wed, Mar 30, 2011 at 10:17 AM, Mohit Anch= lia <mohitanchlia@gmail.com> wrote:
Are you referrring to GTM or LTM. I have looked into it and even
talked to F5 but currently they don't have this functionality for
Prod.

On Tue, Mar 29, 2011 at 4:16 PM, Igor Cicimov <icicimov@gmail.com> wrote:
> Hi guys,
>
> Just scanned through the thread quickly so not sure if this makes any = sense
> but what about F5 source IP stickiness?
>
> Cheers,
> Igor
>
> On Wed, Mar 30, 2011 at 3:34 AM, Mohit Anchlia <mohitanchlia@gmail.com>
> wrote:
>>
>> Currently, the load balancer don't provide the user
>> stickyness/persistence for 'x' amount of time. At this poi= nt only
>> option I see is that of creating a custom solution. It looks like<= br> >> there is no good solution.
>>
>> Problem here is User can be directed to any site by load balancer = in
>> active active scenario where load is being balanced as 1:1 ratio.<= br> >>
>> Cookie was a good option but doesn;t work for non-browser client w= here
>> browser connection to server A and then server A then make Http >> request. So in essence it's the ip of server A that is making = the
>> request and there is no way to use cookies in such scenarios.
>>
>> On Tue, Mar 29, 2011 at 7:25 AM, Ben Timby <btimby@gmail.com> wrote:
>> > On Mon, Mar 28, 2011 at 10:42 PM, Mohit Anchlia <mohitanchlia@gmail.com= >
>> > wrote:
>> >> Thanks! We are using F5 GTM as global load balancer with = LTM. So
>> >> global load balancing is not a problem. Problem is user s= tickyness
>> >> that need to persist beyond individual session.
>> >>
>> >> I forgot to mention that the problem is that these connec= tions come
>> >> from the servers using http rather than browser and that&= #39;s why cookies
>> >> here will probably not work.
>> >
>> > Then you will have to review your load balancer docs and see = what
>> > options are available and go from there. A common load balanc= ing
>> > method is SOURCE, where the source of the request is hashed t= o
>> > determine the backend server to direct the request to. This w= ould
>> > ensure the same source always hits the same backend (as long = as it is
>> > available). The downside to this method is that upstream prox= ies hide
>> > the client's IP address and undermine the load balancing = effectiveness
>> > of this method. However, you know the user (or group of users= ) will be
>> > sticky.
>> >
>>
>> ------------------------------------------------------------------= ---
>> The official User-To-User support forum of the Apache HTTP Server = Project.
>> See <URL:http://httpd.apache.org/userslist.html> for more info= .
>> To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
>> =A0 " =A0 from the digest: users-digest-unsubscribe@httpd= .apache.org
>> For additional commands, e-mail: users-help@httpd.apache.org
>>
>
>

---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.<= br> See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
=A0 " =A0 from the digest: users-digest-unsubscribe@httpd.apache.= org
For additional commands, e-mail: users-help@httpd.apache.org



--0016362844ac2feca3049fa7f80a--