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 etamme@gmail.com designates
 209.85.161.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:content-transfer-encoding;
        b=FASfgxx/gph/jMpnElMi0jvxYgadPotlFgOOklVlB/KPOROvS1Ac3M603R1MKGkS/j
         ebtlXVS90X5nbfTHLtcdawyJFRmG7ZqKzdyWt4PZvEyecy3mw6xUFkPk+GygeR+P5+2W
         kcXSrgwt9Y/17RibYEBDO5Oq2sRCbEggtHmso=
MIME-Version: 1.0
In-Reply-To: <FD7FD634-1DB4-4DE0-A5DD-8B46D4AADA05@thelastpickle.com>
References: <BANLkTinG=nJ4Daf2HXnOe4F=h6B4T1kHHw@mail.gmail.com>
	<573A3685-7221-4AD4-AA9E-2E886B285F6E@thelastpickle.com>
	<BANLkTinKXGJ-t6vuM8K4cFw6ykn_7eLbjg@mail.gmail.com>
	<FD7FD634-1DB4-4DE0-A5DD-8B46D4AADA05@thelastpickle.com>
Date: Mon, 9 May 2011 07:32:46 -0400
Message-ID: <BANLkTi=pPVsHdkbHPSUoYA-B-4MjgbWQNg@mail.gmail.com>
Subject: Re: RequestResponseStage Assertion Error
From: Eric tamme <etamme@gmail.com>
To: user@cassandra.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Mon, May 9, 2011 at 7:18 AM, aaron morton <aaron@thelastpickle.com> wrot=
e:
> You can check the schema using cassandra-cli, run "describe cluster" it w=
ill
> tell you how many schemas are defined.
> I think the best approach when you discover bad schemas is to drain then
> stop the affected node, remove the Location, Migrations and Schema files =
in
> the System data directory, restart and let gossip tell the node whats new=
.
> Note this will also remove the nodes initial token, which will be read ag=
ain
> from the config file.
> I've cannot remember hearing about a better solution.
> The errors are probably=A0http://wiki.apache.org/cassandra/FAQ#jna
> Hope that helps.


Hmm.. nope just checked - all nodes are on the same schema.  As far as
what the error means, I meant what is "RequestResponseStage Assertion
Error"  It does not seem to be critical, as the cluster is operating
"normally" except for the errors printing out on this node.

Any other thoughts?

Thanks again,
Eric