Rob, The JIRA https://issues.apache.org/jira/browse/CASSANDRA-4446 refers to the problem after we've invoked drain. However, we did not invoke drain or flush. We are running one node cassandra within one data center and it is being replicated with another node in another data center. We are using the thrift API in java application to retrieve and modify the data from the primary node only. We are not using the other node in the other data center for any operations. The data loss well exceeds the commit log sync period.
Thanks, Ankit On Mon, Nov 24, 2014 at 8:53 PM, Robert Coli <rc...@eventbrite.com> wrote: > On Mon, Nov 24, 2014 at 5:51 PM, Robert Coli <rc...@eventbrite.com> wrote: > >> What is your replication factor? What CL are you using to read? >> > > Ah, I see from OP that RF is 1. > > As a general statement, RF=1 is an edge case which very, very few people > have ever operated in production. It is relatively likely that there are > some undiscovered edge cases which relate to it. > > That said, this would be a particularly glaring one, which I would expect > to be discovered in other contexts. > > =Rob > >
