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: domain of dan.hendry.junk@gmail.com
 designates 209.85.212.44 as permitted sender)
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=fCsUiYOY5EF03mfpHOlj9ovq1+yh55Id3+gBukIP/bCMN/QFUdq4Md/sTJyVIgVaWf
         qcenNFCtLXZiwufrrb/opekND4VyLS6P/6mPLWvOOguONxYhHRCP1fa5C4BY/vGLfQh6
         ehICX/sKPFSCn1xxuvIrytlXTTkADtd0JtqzA=
MIME-Version: 1.0
In-Reply-To: <AANLkTik6LaATSER30Q5t+2bh5W+oAjig63myXAB6-jCV@mail.gmail.com>
References: <AANLkTik6LaATSER30Q5t+2bh5W+oAjig63myXAB6-jCV@mail.gmail.com>
Date: Thu, 23 Dec 2010 18:35:44 -0500
Message-ID: <AANLkTinagBA5-D-KdnYF9t0LUdkP3K-HirPTbKWhhbj7@mail.gmail.com>
Subject: Re: Having trouble getting cassandra to stay up
From: Dan Hendry <dan.hendry.junk@gmail.com>
To: user@cassandra.apache.org
Content-Type: multipart/alternative; boundary=90e6ba53a01e1892ec04981c5459

--90e6ba53a01e1892ec04981c5459
Content-Type: text/plain; charset=ISO-8859-1

Your details are rather vague, what do you mean by killed? Is the Cassandra
java process still running? Any other warning or error log messages (from
either node)? Could you provide the last few Cassandra log lines from each
machine? Can you connect to the node via JMX? What is the output of nodetool
ring from the second node (which is presumably still alive)? Is there any
unusual system activity: high cpu usage, low cpu usage, problems with disk
IO (can be checked with vmstat).

Can you provide any further system information? Linux/windows, java version,
32/64 bit, amount of ram?

On Thu, Dec 23, 2010 at 1:42 PM, Alex Quan <alex.quan@tinkur.com> wrote:

> 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
>

--90e6ba53a01e1892ec04981c5459
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Your details are rather vague, what do you mean by killed? Is the Cassandra=
 java process still running? Any other warning or error log messages (from =
either node)? Could you provide the last few Cassandra log lines from each =
machine? Can you connect to the node via JMX? What is the output of nodetoo=
l ring from the second node (which is presumably still alive)? Is there any=
 unusual system activity: high cpu usage, low cpu usage, problems with disk=
 IO (can be checked with vmstat).<div>
<br></div><div>Can you provide any further system information? Linux/window=
s, java version, 32/64 bit, amount of ram?=A0<br><br><div class=3D"gmail_qu=
ote">On Thu, Dec 23, 2010 at 1:42 PM, Alex Quan <span dir=3D"ltr">&lt;<a hr=
ef=3D"mailto:alex.quan@tinkur.com">alex.quan@tinkur.com</a>&gt;</span> wrot=
e:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex;">Hi,<br><br>I am a newbie to cassandra and a=
m using cassandra RC 2. I initially have cassndra working on one node and w=
as 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 af=
ter that I couldn&#39;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:<br>

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

Killed<br><br>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&#39;t know what=
 to try to get it to work properly, if you guys can help I would be really =
grateful<br>
<font color=3D"#888888">
<br>Alex<br><div style=3D"display:inline"></div>
</font></blockquote></div><br></div>

--90e6ba53a01e1892ec04981c5459--