On Mon, Nov 24, 2014 at 3:19 PM, Ankit Patel <ankit7...@gmail.com> wrote:
> We are experiencing data loss with Cassandra 1.0.10 when we had restarted > the without flushing. We see in the cassandra logs that the commitlogs were > read back without any problems. Until the restart the data was correct. > However, after the node restarted we retrieved older version of the data > (row caching is turned off). We are reading/writing to a single cassandra > node that is replicated to a single node setup at another data center. The > times are synchronized across our machines. Has anyone experienced this > type of behavior? > I'm not sure I've heard of a particular issue where data is not correctly replayed after restart. But 1.0.10 is the era of : https://issues.apache.org/jira/browse/CASSANDRA-4446 "nodetool drain sometimes doesn't mark commitlog fully flushed" ... and there have been other bugs relating to commitlog replay since... What is your replication factor? What CL are you using to read? If you look in SStables on the affected node, which versions of the row exist? =Rob
