I'll try and report in September (I'm "on vacation" but trying to get the cluster to run !).
Thanks 2011/8/16 Jonathan Ellis <jbel...@gmail.com> > Probably not. In fact, I can't think of a scenario where truncated > data could reappear w/o a restart, assuming the truncate completes > successfully on all nodes. Is this 0.8.4? Can you reproduce with a > toy cluster using https://github.com/pcmanus/ccm ? > > On Tue, Aug 16, 2011 at 9:44 AM, Philippe <watche...@gmail.com> wrote: > > The title and the comments describe a node restarting. This is not my > case. > > could it still be the same thing ? > > As always, I appreciate the quick answers you guys provide ! > > > > 2011/8/16 Jonathan Ellis <jbel...@gmail.com> > >> > >> https://issues.apache.org/jira/browse/CASSANDRA-2950 > >> > >> On Tue, Aug 16, 2011 at 8:45 AM, Philippe <watche...@gmail.com> wrote: > >> > Hello, what are the guarantees regarding truncates issued through the > >> > CLI ? > >> > I have a 3 node ring at RF=3. No writes going to the keyspace at issue > >> > here. > >> > I go to the CLI on one of the nodes and issue a truncate on all CF of > >> > the > >> > keyspace. I run a list [CF] and make sure there is no data. > >> > When I run a repair on that node & keyspace, data appears back into > the > >> > CFs. > >> > Why is that ? > >> > Thaks > >> > >> > >> > >> -- > >> Jonathan Ellis > >> Project Chair, Apache Cassandra > >> co-founder of DataStax, the source for professional Cassandra support > >> http://www.datastax.com > > > > > > > > -- > Jonathan Ellis > Project Chair, Apache Cassandra > co-founder of DataStax, the source for professional Cassandra support > http://www.datastax.com >
