Return-Path: X-Original-To: apmail-cassandra-user-archive@www.apache.org Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id F141C98AB for ; Wed, 23 Nov 2011 00:57:39 +0000 (UTC) Received: (qmail 49769 invoked by uid 500); 23 Nov 2011 00:57:37 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 49717 invoked by uid 500); 23 Nov 2011 00:57:37 -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 49709 invoked by uid 99); 23 Nov 2011 00:57:37 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 23 Nov 2011 00:57:37 +0000 X-ASF-Spam-Status: No, hits=1.3 required=5.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS,URI_HEX X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of mrlalonde@live.ca designates 65.54.190.144 as permitted sender) Received: from [65.54.190.144] (HELO bay0-omc3-s6.bay0.hotmail.com) (65.54.190.144) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 23 Nov 2011 00:57:29 +0000 Received: from BAY160-W42 ([65.54.190.189]) by bay0-omc3-s6.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Tue, 22 Nov 2011 16:57:09 -0800 Message-ID: X-Originating-IP: [99.240.215.148] From: Mathieu Lalonde To: Subject: DataCenters each with their own local data source Date: Tue, 22 Nov 2011 19:57:09 -0500 Importance: Normal Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginalArrivalTime: 23 Nov 2011 00:57:09.0314 (UTC) FILETIME=[D3E70A20:01CCA97A] Hi=2C I am wondering if Cassandra's features and datacenter awareness can help me= with my scalability problems. Suppose that I have a 10-20 Data centers=2C each with their own local (mass= ive) source of time series data.=A0 I would like: - to avoid replication across data centers (this seems doable based on: htt= p://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Different-Key= Spaces-for-different-nodes-in-the-same-ring-td5096393.html#a5096568 ) - writes for local data to be done on the local data center (not sure about= that one) - reads from a master data center to any remote data centers (not sure abou= t that one either) It sounds like I am trying to use Cassandra in a very different way that it= was intended to be used. Should I simply have a middle-tier that takes care of distributing reads to= multiple data centers and treat each data center as its own autonomous clu= ster? Thanks! Matt =