Return-Path: Delivered-To: apmail-incubator-cassandra-user-archive@minotaur.apache.org Received: (qmail 37578 invoked from network); 2 May 2009 16:20:51 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 2 May 2009 16:20:51 -0000 Received: (qmail 50414 invoked by uid 500); 2 May 2009 16:20:51 -0000 Delivered-To: apmail-incubator-cassandra-user-archive@incubator.apache.org Received: (qmail 50377 invoked by uid 500); 2 May 2009 16:20:51 -0000 Mailing-List: contact cassandra-user-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: cassandra-user@incubator.apache.org Delivered-To: mailing list cassandra-user@incubator.apache.org Received: (qmail 50368 invoked by uid 99); 2 May 2009 16:20:51 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 02 May 2009 16:20:51 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of manuel.crotti@ing.unibs.it designates 192.167.23.204 as permitted sender) Received: from [192.167.23.204] (HELO hiems2.ing.unibs.it) (192.167.23.204) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 02 May 2009 16:20:42 +0000 Received: from localhost (localhost [127.0.0.1]) by hiems2.ing.unibs.it (Postfix) with ESMTP id 4F658182552C for ; Sat, 2 May 2009 18:20:22 +0200 (CEST) X-Virus-Scanned: amavisd-new at ing.unibs.it Received: from hiems2.ing.unibs.it ([127.0.0.1]) by localhost (hiems1.ing.unibs.it [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id N384bmO6vH+f for ; Sat, 2 May 2009 18:20:22 +0200 (CEST) X-PreSpam: auth Message-Id: <55B3B63F-91D2-4C8C-9418-2D696213716C@ing.unibs.it> From: Manuel Crotti To: cassandra-user@incubator.apache.org In-Reply-To: Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v930.3) Subject: Re: Some questions. Date: Sat, 2 May 2009 18:20:20 +0200 References: <75F7AE08-430D-4430-B0F9-6736FEA48129@ing.unibs.it> X-Mailer: Apple Mail (2.930.3) X-Virus-Checked: Checked by ClamAV on apache.org Hi Jonathan, Thanks for the fast reply. >> [cut] > Right. The only thing you that should be different is the > ListenAddress section. (You can try leaving that out and Cassandra > will pick an interface to use but it often guesses a non-public > interface which is not helpful. :) Changed to public interface, now it shows all the nodes. :) > > >> 3.2 finally: should I start a cluster with an empty DB or I can >> replicate an >> existing DB? > > You can start from an existing one if it's really legitimate for all > nodes to have copies of that data but it probably is not. Ok, since each node had the same token (and sounded quite strange), I emptied the /var/cassandra folder. Restarting the service, each node took a different token. Was it correct? Now a strange thing (please be patient, I'm a newbie): Inserted a set of pairs (data,key) running "cassandra-cli" from host 10.0.1.1 Then: ./bin/cassandra-cli --host 10.0.1.2 cassandra> get Table1.Standard1['foo'] COLUMN_TIMESTAMP = 1241219309914; COLUMN_VALUE = data; COLUMN_KEY = bar; COLUMN_TIMESTAMP = 1241218702595; COLUMN_VALUE = data2; COLUMN_KEY = bar2; COLUMN_TIMESTAMP = 1241211956945; COLUMN_VALUE = data3; COLUMN_KEY = bar3; then: ./bin/cassandra-cli --host 10.0.1.3 cassandra> get Table1.Standard1['foo'] COLUMN_TIMESTAMP = 1241219309914; COLUMN_VALUE = data; COLUMN_KEY = bar; COLUMN_TIMESTAMP = 1241218702595; COLUMN_VALUE = data2; COLUMN_KEY = bar2; COLUMN_TIMESTAMP = 1241211956945; COLUMN_VALUE = data3; COLUMN_KEY = bar3; Ok, it's GREAT (I'm querying the cluster from different servers, right?) If I try the same via web interface, it works only on nodes 10.0.1.1 and 10.0.1.3. "Success: Key = foo ... " on 10.0.1.2: "Error: Key [foo], column family [Standard1] not found." Any idea? > >> I also submit a couple of errors that raised using the command-line >> client: > > Okay, so the problems are that (1) it thinks it is connected when it > is not, and (2) it allows you to run commands when it is not > connected. Right? Not exactly. "show config file" causes the client disconnection from each of the nodes. I'll take a look into the issue tracker. > Can you file those in the issue tracker? > https://issues.apache.org/jira/browse/CASSANDRA > > thanks, > > -Jonathan BR, Manuel.