This is the same behavior I reported in 2768 as Aaron referenced ... What was suggested for us was to do the following:
- Shut down the entire ring - When you bring up each node, do a nodetool repair That didn't immediately resolve the problems. In the end, I backed up all the data, removed the keyspace and created a new one. That seemed to have solved our problems. That was from 0.7.6-2 to 0.8.0 However, in the issue reported, it was unable to be reproduced ... I'd be curious to know how Hector's keyspace is defined. Ours at the time was RF=3 and using Ec2 snitch... -sd On Fri, Jul 1, 2011 at 9:22 AM, Sylvain Lebresne <sylv...@datastax.com> wrote: > Héctor, when you say "I have upgraded all my cluster to 0.8.1", from > which version was > that: 0.7.something or 0.8.0 ? > > If this was 0.8.0, did you run successful repair on 0.8.0 previous to > the upgrade ?
