Return-Path: Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: (qmail 59265 invoked from network); 23 Dec 2010 18:42:41 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 23 Dec 2010 18:42:41 -0000 Received: (qmail 863 invoked by uid 500); 23 Dec 2010 18:42:39 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 800 invoked by uid 500); 23 Dec 2010 18:42:38 -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 792 invoked by uid 99); 23 Dec 2010 18:42:38 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 23 Dec 2010 18:42:38 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [74.125.82.172] (HELO mail-wy0-f172.google.com) (74.125.82.172) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 23 Dec 2010 18:42:30 +0000 Received: by wyf23 with SMTP id 23so6494322wyf.31 for ; Thu, 23 Dec 2010 10:42:09 -0800 (PST) MIME-Version: 1.0 Received: by 10.216.179.81 with SMTP id g59mr12398901wem.35.1293129721214; Thu, 23 Dec 2010 10:42:01 -0800 (PST) Received: by 10.216.254.136 with HTTP; Thu, 23 Dec 2010 10:42:01 -0800 (PST) X-Originating-IP: [68.146.243.160] Date: Thu, 23 Dec 2010 11:42:01 -0700 Message-ID: Subject: Having trouble getting cassandra to stay up From: Alex Quan To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=0016364162a9ae80b10498183933 --0016364162a9ae80b10498183933 Content-Type: text/plain; charset=ISO-8859-1 Hi, I am a newbie to cassandra and am using cassandra RC 2. I initially have cassndra working on one node and was able to create keyspace, column families and populate the database fine. I tried adding a second node by changing the seed to point to another node and setting listen_address and rpc_address to blank. I then started up the second node and it seems to have connected fine using the node tool but after that I couldn't get it to accept any commands and whenever I tried to make a new keyspace or column family it would kill my initial node after a message like this: INFO 18:19:49,335 switching in a fresh Memtable for Schema at CommitLogContext(file='/var/lib/cassandra/commitlog/CommitLog-1293127746481.log', position=9143) INFO 18:19:49,335 Enqueuing flush of Memtable-Schema@1358138608(2410 bytes, 5 operations) Killed and the next few time I start up the server a similar would pop up until I am guessing all the stuff is flushed out then it would start fine until I tried to add anything to it. I tried changing back the yaml file back to the original setup and this still happens. I don't know what to try to get it to work properly, if you guys can help I would be really grateful Alex --0016364162a9ae80b10498183933 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi,

I am a newbie to cassandra and am using cassandra RC 2. I initia= lly have cassndra working on one node and was able to create keyspace, colu= mn families and populate the database fine. I tried adding a second node by= changing the seed to point to another node and setting listen_address and = rpc_address to blank. I then started up the second node and it seems to hav= e connected fine using the node tool but after that I couldn't get it t= o accept any commands and whenever I tried to make a new keyspace or column= family it would kill my initial node after a message like this:

=A0INFO 18:19:49,335 switching in a fresh Memtable for Schema at Commit= LogContext(file=3D'/var/lib/cassandra/commitlog/CommitLog-1293127746481= .log', position=3D9143)
=A0INFO 18:19:49,335 Enqueuing flush of Memt= able-Schema@1358138608(2410 bytes, 5 operations)
Killed

and the next few time I start up the server a similar would p= op up until I am guessing all the stuff is flushed out then it would start = fine until I tried to add anything to it. I tried changing back the yaml fi= le back to the original setup and this still happens. I don't know what= to try to get it to work properly, if you guys can help I would be really = grateful

Alex
--0016364162a9ae80b10498183933--