Return-Path: X-Original-To: apmail-trafficserver-users-archive@www.apache.org Delivered-To: apmail-trafficserver-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 3BBFE10846 for ; Thu, 17 Apr 2014 18:49:13 +0000 (UTC) Received: (qmail 45161 invoked by uid 500); 17 Apr 2014 18:49:12 -0000 Delivered-To: apmail-trafficserver-users-archive@trafficserver.apache.org Received: (qmail 45054 invoked by uid 500); 17 Apr 2014 18:49:12 -0000 Mailing-List: contact users-help@trafficserver.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@trafficserver.apache.org Delivered-To: mailing list users@trafficserver.apache.org Received: (qmail 45046 invoked by uid 99); 17 Apr 2014 18:49:11 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 17 Apr 2014 18:49:11 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of h.reindl@thelounge.net designates 91.118.73.15 as permitted sender) Received: from [91.118.73.15] (HELO mail.thelounge.net) (91.118.73.15) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 17 Apr 2014 18:49:06 +0000 Message-ID: <5350220C.5010608@thelounge.net> Date: Thu, 17 Apr 2014 20:48:44 +0200 From: Reindl Harald Organization: the lounge interactive design User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: users@trafficserver.apache.org Subject: Re: ATS x datacenter(s) References: In-Reply-To: X-Enigmail-Version: 1.6 OpenPGP: id=7F780279; url=http://arrakis.thelounge.net/gpg/h.reindl_thelounge.net.pub.txt Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="xETsaJwpSAFuKp3Pe3453TLEV0KOTtOTd" X-Virus-Checked: Checked by ClamAV on apache.org This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --xETsaJwpSAFuKp3Pe3453TLEV0KOTtOTd Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Am 17.04.2014 20:41, schrieb Bacon Tuna: > I haven't had luck finding white papers or documentation discussing str= ategies for running ATS clusters across > multiple data centers or availability zones to support high availabilit= y? >=20 > Any chance someone on here can point me in the right direction? >=20 > Do people load balance multiple clusters with separate caches, or do th= ey employ some mechanism to maintain > consistency across regions? i would let caches alone, it get's filled alone and has no imprtant data if you only have one backend and some ATS for load-balancing you are completly fine - your spread your load and take a lot of away from the backend server possible resulting in you have no need for more backend servers - the high ability itself of the backend can by something like VMware HA or whatever doing failover if you need more than one backendserver you should take much more care to keep sessions between the backends synchronous to avoid troubles having one request of the same client on two different backend servers and log the client out --xETsaJwpSAFuKp3Pe3453TLEV0KOTtOTd Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlNQIgwACgkQhmBjz394Ank3qACcD5gnLhpGLDGAGuo080N6wv/E D+8AoJjPByIIzI+hcLWX5H7Ru1A4ezeS =Vbm0 -----END PGP SIGNATURE----- --xETsaJwpSAFuKp3Pe3453TLEV0KOTtOTd--