Return-Path: Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: (qmail 27759 invoked from network); 23 Apr 2010 23:18:18 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 23 Apr 2010 23:18:18 -0000 Received: (qmail 87762 invoked by uid 500); 23 Apr 2010 23:18:18 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 87662 invoked by uid 500); 23 Apr 2010 23:18:18 -0000 Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@cassandra.apache.org Delivered-To: mailing list user@cassandra.apache.org Received: (qmail 87653 invoked by uid 99); 23 Apr 2010 23:18:18 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 23 Apr 2010 23:18:18 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of banksenus@gmail.com designates 209.85.160.44 as permitted sender) Received: from [209.85.160.44] (HELO mail-pw0-f44.google.com) (209.85.160.44) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 23 Apr 2010 23:18:11 +0000 Received: by pwj2 with SMTP id 2so7333188pwj.31 for ; Fri, 23 Apr 2010 16:17:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=ztnCfRLfX7HWC+BnpideH93V9hpJdLG3N0jIlCxIZH8=; b=mutLw03RdlYPX/fucEu9TEnONxvB2XvZlrGttXHiGlbEFfkyRfogA0okI0W5XSU6xu eWordexaJho/7uNlPdTi8D1MBJ+dILYDJsJt9/Anfcb2xIyWsjx3Tntz+UtlGqzi0AWt mjMB49Td4d/+/mNBE3DxYTgac92P+xzTc6xc8= 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=V/cTMpqZ4KeEoz74GsOPhWLM1D6HRBxm9cioum+DFzEoX7oBeuVOwYLZrubrUChS/I bRlFuqfMYE/H3gtPp9VDfE/SnxGV/XnAnF0/MKuPngwxgw8IanrPLsobAi06KIjerZji g8VloacbtiMIO9zYTmbgOAVwB3r7loX0RveHA= MIME-Version: 1.0 Received: by 10.142.10.1 with SMTP id 1mr193871wfj.110.1272064669924; Fri, 23 Apr 2010 16:17:49 -0700 (PDT) Received: by 10.142.143.15 with HTTP; Fri, 23 Apr 2010 16:17:49 -0700 (PDT) In-Reply-To: References: <1272031807.62476.ezmlm@cassandra.apache.org> Date: Fri, 23 Apr 2010 16:17:49 -0700 Message-ID: Subject: Re: Question about a potential configuration scenario From: banks To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=00504502acf4c83fdd0484efa28f X-Virus-Checked: Checked by ClamAV on apache.org --00504502acf4c83fdd0484efa28f Content-Type: text/plain; charset=ISO-8859-1 just make them one cluster, and use the rackAware logic... On Fri, Apr 23, 2010 at 7:21 AM, Campbell, Joseph < Joseph_Campbell@comcast.com> wrote: > Question: > It is possible to setup Cassandra such that 2 independent > Cassandra rings/clusters replicate to one another, ensuring that each > ring/cluster has at least 1 copy of all the data on each ring/cluster? > > The setup is like this: > 2 Data centers, one in Philadelphia and another in Denver. In > each data center there exists a Cassandra ring/cluster. Each data > center is being used as a live-live origin (meaning both data centers > are in use at any point in time). I would like to be able to guarantee > that in the event that one or the other of the data centers goes down > that 'ALL' the available data in that failed data center is also > available in the other data center such that traffic to the origin > website that depends on the data can simply be switched over to the > other site (Using Akamai, or other tools). Is this type of > configuration possible/available in Cassandra? If so how would you set > it up, and what might some of the draw backs be? > > Thanks, > Joe Campbell > > > > -- > Anyone can get hit by a MOVING car, > but it takes skill to get hit by a PARKED car. > -- Random Tee-shirt on Dysfunction > > Joe Campbell | one comcast center | philadelphia, pa 19103 | > 215.286.5073 > --00504502acf4c83fdd0484efa28f Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable just make them one cluster, and use the rackAware logic...

On Fri, Apr 23, 2010 at 7:21 AM, Campbell, Joseph <Joseph_Campbe= ll@comcast.com> wrote:
Question:
=A0 =A0 =A0 =A0It is possible to setup Cassandra such that 2 independent Cassandra rings/clusters replicate to one another, ensuring that each
ring/cluster has at least 1 copy of all the data on each ring/cluster?

The setup is like this:
=A0 =A0 =A0 =A02 Data centers, one in Philadelphia and another in Denver. = =A0In
each data center there exists a Cassandra ring/cluster. =A0Each data
center is being used as a live-live origin (meaning both data centers
are in use at any point in time). =A0I would like to be able to guarantee that in the event that one or the other of the data centers goes down
that 'ALL' the available data in that failed data center is also available in the other data center such that traffic to the origin
website that depends on the data can simply be switched over to the
other site (Using Akamai, or other tools). =A0Is this type of
configuration possible/available in Cassandra? =A0If so how would you set it up, and what might some of the draw backs be?

Thanks,
=A0 =A0 =A0 =A0Joe Campbell



--
Anyone can get hit by a MOVING car,
but it takes skill to get hit by a PARKED car.
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 -- Random Tee-shirt on Dysfunction=

Joe Campbell | one comcast center | philadelphia, pa 19103 |
215.286.5073

--00504502acf4c83fdd0484efa28f--