Return-Path: Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: (qmail 47164 invoked from network); 5 May 2010 14:43:47 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 5 May 2010 14:43:47 -0000 Received: (qmail 61132 invoked by uid 500); 5 May 2010 14:43:42 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 61097 invoked by uid 500); 5 May 2010 14:43:42 -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 61016 invoked by uid 99); 5 May 2010 14:43:42 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 05 May 2010 14:43:42 +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 (athena.apache.org: domain of congo.chang@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; Wed, 05 May 2010 14:43:36 +0000 Received: by pwj2 with SMTP id 2so2638687pwj.31 for ; Wed, 05 May 2010 07:43:16 -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=FIkXwNkaZ1iAsQkMYvQ5ipVrDUlheOMjFvn/unSLcJw=; b=XNMoElg2U7Q2LGpu/yv2NTF1qlKovt86OHkJDGkM0WlWvDCnX9iLkWhokq76v+WUSU UWdWTrpJD2zc8JPOxDVn5gGUbXsOAGPTGxLbP6ba2Jm9owy5/1iydPzFBkRUhv/1k+0t IotdXTfMTG4B3FySjH7rLhdLVflYboysqKYcw= 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=pZ0bnlvOLErPnufrnFoeJIuFYTuMF/YCrCysMqEu8mkY2JseepBpz7/qWHVzSc3o5G gb/QlocIoIlAL8HTrwHNITc/ncPER310JP84BtYfh1bwgXZ10cUBgkiDZQefKKxU+yWi XibBKXiq6M7+EqkLPVq1lPcT/zYqAWMTpockI= MIME-Version: 1.0 Received: by 10.141.108.10 with SMTP id k10mr5820574rvm.113.1273070596172; Wed, 05 May 2010 07:43:16 -0700 (PDT) Received: by 10.141.3.12 with HTTP; Wed, 5 May 2010 07:43:16 -0700 (PDT) In-Reply-To: References: Date: Wed, 5 May 2010 22:43:16 +0800 Message-ID: Subject: Re: Add a new keyspace in cassandra cluster From: Yu-Chun Chang To: user@cassandra.apache.org, gdusbabek@gmail.com Content-Type: multipart/alternative; boundary=000e0cd137f8a8ac800485d9d845 --000e0cd137f8a8ac800485d9d845 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Thank you very much for your help! Best regards, Yu-Chun On Wed, May 5, 2010 at 8:51 PM, Gary Dusbabek wrote: > Yes. You need to edit the configuration of every machine in the cluster. > > Gary. > > On Wed, May 5, 2010 at 06:27, Yu-Chun Chang wrote= : > > Dear all, > > I'm a starter for playing Cassandra. I've set up three machines (called > > PC_A, PC_B, PC_C) and run them as a Cassandra cluster. > > I've inserted a record in the running cluster and saw it did work throu= gh > > three machines. > > Then I shutdowned Cassandra of PC_A, and modified storage-conf.xml to a= dd > > new keyspace (called new1). The new record and new > > keyspace (new1) were displayed in PC_A after restarting Cassandra. But = I > > cannot see the new keyspace (new1) added in PC_B and > > PC_C. Do I miss the procedure of running the cluster or have to modify > the > > same config in both PC_B and PC_C ? > > Many thanks. > > Best regards, > > Yu-Chun > > > > > --=20 Yu-Chun Chang =E5=BC=B5=E8=A3=95=E9=88=9E PhD student Department of Electrical Engineering National Taiwan University --000e0cd137f8a8ac800485d9d845 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Thank you very much for your help!

Best regar= ds,
Yu-Chun

On Wed, May 5, 2010 at 8= :51 PM, Gary Dusbabek <gdusbabek@gmail.com> wrote:
Yes. =C2=A0You need to edit the configurati= on of every machine in the cluster.

Gary.

On Wed, May 5, 2010 at 06:27, Yu-Chun Chang <congo.chang@gmail.com> wrote:
> Dear all,
> I'm a starter for playing Cassandra. I've set up three machine= s (called
> PC_A, PC_B, PC_C) and run them as a Cassandra cluster.
> I've inserted a record in the running cluster and saw it did work = through
> three machines.
> Then=C2=A0I shutdowned Cassandra of PC_A, and=C2=A0modified storage-co= nf.xml=C2=A0to add
> new=C2=A0keyspace (called new1). The new=C2=A0record and new
> keyspace (new1) were displayed in PC_A=C2=A0after restarting Cassandra= . But=C2=A0I
> cannot see=C2=A0the new keyspace (new1) added in PC_B and
> PC_C. Do I miss the procedure of running the cluster or have to modify= the
> same config in both PC_B and PC_C ?
> Many thanks.
> Best regards,
> Yu-Chun
>
>



--
Yu-Chun Cha= ng =E5=BC=B5=E8=A3=95=E9=88=9E
PhD student
Department of Electrical E= ngineering
National Taiwan University

--000e0cd137f8a8ac800485d9d845--