Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: pass (nike.apache.org: local policy)
DomainKey-Signature: a=rsa-sha1; c=nofws; d=thelastpickle.com; h=subject
	:references:from:content-type:in-reply-to:message-id:date:to
	:content-transfer-encoding:mime-version; q=dns; s=
	thelastpickle.com; b=WZr5AVAjxycC7gUy9kFAkcodLfwAXyPBiR5lc+nOpZ/
	thDeq4SMVivyxRQU3YK8Vt1IEZh9dvWRx4wXDdEK4mtXLGWwVnemzgHr+H/eGAcR
	Npt3RudkDNWxz8J+7QJWTaPEPuB6SZpWUgQFxJZiJuPd6CH/p6Dhk08bY7pRhrUA
	=
Subject: Re: Running hadoop jobs against data in remote data center
References: 
 <CA+OgoCuiZ-mUUZ-6MK8+dQWY_etuYAXk8pb+JBkt94GqgCPMSw@mail.gmail.com>
From: Aaron Morton <aaron@thelastpickle.com>
Content-Type: text/plain;
	charset=us-ascii
In-Reply-To: 
 <CA+OgoCuiZ-mUUZ-6MK8+dQWY_etuYAXk8pb+JBkt94GqgCPMSw@mail.gmail.com>
Message-Id: <A577EFBF-BD29-41DE-A73E-62180574051A@thelastpickle.com>
Date: Thu, 7 Jul 2011 14:23:54 +1200
To: "user@cassandra.apache.org" <user@cassandra.apache.org>
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (iPad Mail 8J3)

See http://www.datastax.com/dev/blog/deploying-cassandra-across-multiple-dat=
a-centers and http://www.datastax.com/docs/0.8/brisk/about_brisk#about-the-b=
risk-architecture

It's possible to run multi DC and use LOCAL_QUORUM consistency level in your=
 production centre to allow the prod code to get on with it's life without w=
orrying about the other DC.

Hope that helps.


-----------------
Aaron Morton
Freelance Cassandra Developer
@aaronmorton
http://www.thelastpickle.com

On 7/07/2011, at 1:29 PM, Jason Baker <jason@apture.com> wrote:

> I'm just setting up a Cassandra cluster for my company.  For a variety of r=
easons, we have the servers that run our hadoop jobs in our local office and=
 our production machines in a collocated data center.  We don't want to run h=
adoop jobs against cassandra servers on the other side of the US from us, no=
t to mention that we don't want them impacting performance in production.  W=
hat's the best way to handle this?
>=20
> My first instinct is to add some servers locally to the node and use Netwo=
rkTopologyStrategy.  This way, the servers automatically get updated with th=
e latest changes, and we get a bit of extra redundancy for our production ma=
chine.  Of course, the glaring weakness of this strategy is that our stats s=
ervers aren't in a datacenter with any kind of production guarantees.  The n=
etwork connection is relatively slow and unreliable, the servers may go out a=
t any time, and I generally don't want to tie our production performance or r=
eliability to these servers.
>=20
> Is this as dumb an idea as I suspect it is, or can this be made to work?  :=
-)
>=20
> Are there any better ways to accomplish what I'm trying to accomplish?