cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Eric Czech <e...@nextbigsound.com>
Subject Re: Schema versions reflect schemas on unwanted nodes
Date Fri, 14 Oct 2011 22:51:45 GMT
Well, the schema versions are still apparently consistent across the nodes
that are actually part of the ring (according to "describe cluster").  I
could just upgrade, but I'm trying to hold out for datastax enterprise or at
least community and would rather not have to upgrade to 0.8.7 and then 1.x
like 2 weeks later.

I might be getting a bit too paranoid here though because adding/removing
column families through the cli still appears to be working correctly even
though I get a "schema disagreement error" followed by cli termination with
a warning like "further migrations are ill advised".  I've tried this a
couple times and all newly created column families still seem to function
correctly so I'll just ignore the errors that get thrown until I do the next
upgrade.  Please stop me if that sounds idiotic haha.

On Fri, Oct 14, 2011 at 4:22 PM, Brandon Williams <driftx@gmail.com> wrote:

> On Fri, Oct 14, 2011 at 2:36 PM, Eric Czech <eric@nextbigsound.com> wrote:
> > Thanks again.  I have truncated certain cf's recently and the cli didn't
> > complain and listings of the cf rows return nothing after truncation.  Is
> > that data not actually deleted?
>
> Hmm, well, now I'm confused because if 3259 is your problem truncate
> won't work.  If it did then it sounds like you have a schema
> disagreement problem with nodes that are members of the ring.  If
> truncate didn't return an error it did work, however.
>
> -Brandon
>

Mime
View raw message