Have you tried nodetool resetlocalschema on the 1.1.5 ?
Cheers
-
Aaron Morton
Freelance Developer
@aaronmorton
http://www.thelastpickle.com
On 20/09/2012, at 11:41 PM, Thomas Stets thomas.st...@gmail.com wrote:
A follow-up:
Currently I'm back on version 1.1.1.
I tried -
On Fri, Sep 21, 2012 at 10:39 AM, aaron morton aa...@thelastpickle.comwrote:
Have you tried nodetool resetlocalschema on the 1.1.5 ?
Yes, I tried a resetlocalschema, and a repair. This didn't change anything.
BTW I could find no documentation, what a resetlocalschema actually does...
On Wed, Sep 19, 2012 at 5:12 PM, Michael Kjellman
mkjell...@barracuda.comwrote:
Sounds like you are loosing your system keyspace. When you say nothing
important changed between yaml files do you mean with or without your
changes?
I compared the 1.1.1 cassandra.yaml (with my changes) to the
A follow-up:
Currently I'm back on version 1.1.1.
I tried - unsuccessfully - the following things:
1. Create the missing keyspace on the 1.1.5 node, then copy the files back
into the data directory.
This failed, since the keyspace was already known on the other node in the
cluster.
2. shut
I consistently keep losing my keyspace on upgrading from cassandra 1.1.1 to
1.1.5
I have the same cassandra keyspace on all our staging systems:
development: a 3-node cluster
integration: a 3-node cluster
QS: a 2-node cluster
(productive will be a 4-node cluster, which is as yet not active)
Sounds like you are loosing your system keyspace. When you say nothing
important changed between yaml files do you mean with or without your changes?
Did your data directories change in the migration? Permissions okay?
I've done a 1.1.1 to 1.1.5 upgrade on many of my nodes without issue..
On
We've seen that before too - supposedly it was fixed in 1.1.5. Your
experience casts some doubt on that.
Our workaround, thus far, is to shut down the entire ring and then bring
each node back up starting with known good.
Then you do nodetool resetlocalschema on the node that's confused and
@Edward Do you have a bug number for that by chance?
On Sep 19, 2012, at 8:25 AM, Edward Sargisson
edward.sargis...@globalrelay.netmailto:edward.sargis...@globalrelay.net
wrote:
We've seen that before too - supposedly it was fixed in 1.1.5. Your experience
casts some doubt on that.
Our
https://issues.apache.org/jira/browse/CASSANDRA-4583
On 12-09-19 08:30 AM, Michael Kjellman wrote:
@Edward Do you have a bug number for that by chance?
On Sep 19, 2012, at 8:25 AM, Edward Sargisson
edward.sargis...@globalrelay.netmailto:edward.sargis...@globalrelay.net wrote:
We've seen that
