Blowing away the database does indeed seem to fix the problem, but it doesn't exactly make me feel warm and cozy. I have no idea how the database got screwed up, so I don't know what to avoid doing so that I don't have this happen again on a production server. I never had any other nodes, so it has nothing to do with adding or removing nodes. I guess I just cross my fingers and hope it doesn't happen again.
Thanks Robert From: Aaron Morton <aa...@thelastpickle.com> Reply-To: <user@cassandra.apache.org> Date: Monday, November 25, 2013 12:46 PM To: Cassandra User <user@cassandra.apache.org> Subject: Re: Cannot TRUNCATE If it¹s just a test system nuke it and try again :) Was there more than one node at any time ? Does nodetool status show only one node ? Cheers ----------------- Aaron Morton New Zealand @aaronmorton Co-Founder & Principal Consultant Apache Cassandra Consulting http://www.thelastpickle.com On 21/11/2013, at 7:45 am, Robert Wille <rwi...@fold3.com> wrote: > I've got a single node with all empty tables, and truncate fails with the > following error: Unable to complete request: one or more nodes were > unavailable. > > Everything else seems fine. I can insert, update, delete, etc. > > The only thing in the logs that looks relevant is this: > > INFO [HANDSHAKE-/192.168.98.121] 2013-11-20 11:36:59,064 > OutboundTcpConnection.java (line 386) Handshaking version with /192.168.98.121 > INFO [HANDSHAKE-/192.168.98.121] 2013-11-20 11:37:04,064 > OutboundTcpConnection.java (line 395) Cannot handshake version with > /192.168.98.121 > > I'm running Cassandra 2.0.2. I get the same error in cqlsh as I do with the > java driver. > > Thanks > > Robert
