On Mon, Nov 25, 2013 at 3:35 PM, Robert Wille <rwi...@fold3.com> wrote:
> 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. > [... snip ...] > I'm running Cassandra 2.0.2. I get the same error in cqlsh as I do with > the java driver. > > https://engineering.eventbrite.com/what-version-of-cassandra-should-i-run/ I know this is a slightly glib response, but hopefully whatever bug you triggered will be resolved by the time 2.0.x series is ready to be run in production.. :D =Rob
