cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vincent White (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-14013) Data loss in snapshots keyspace after service restart
Date Fri, 01 Dec 2017 00:17:00 GMT


Vincent White commented on CASSANDRA-14013:

I've create a patch for 3.0.x and trunk using the same method. I guess it should be safe to
work with just absolute paths rather than canonical paths here, I haven't made that change
on the 3.x.x patches yet. I also had to fiddle with the unit tests since there is now a dependancy
on DatabaseDescriptor and passing in file paths that exist in the configured data directory.


> Data loss in snapshots keyspace after service restart
> -----------------------------------------------------
>                 Key: CASSANDRA-14013
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Gregor Uhlenheuer
>            Assignee: Vincent White
> I am posting this bug in hope to discover the stupid mistake I am doing because I can't
imagine a reasonable answer for the behavior I see right now :-)
> In short words, I do observe data loss in a keyspace called *snapshots* after restarting
the Cassandra service. Say I do have 1000 records in a table called *snapshots.test_idx* then
after restart the table has less entries or is even empty.
> My kind of "mysterious" observation is that it happens only in a keyspace called *snapshots*...
> h3. Steps to reproduce
> These steps to reproduce show the described behavior in "most" attempts (not every single
time though).
> {code}
> # create keyspace
> CREATE KEYSPACE snapshots WITH replication = {'class': 'SimpleStrategy', 'replication_factor':
> # create table
> CREATE TABLE snapshots.test_idx (key text, seqno bigint, primary key(key));
> # insert some test data
> INSERT INTO snapshots.test_idx (key,seqno) values ('key1', 1);
> ...
> INSERT INTO snapshots.test_idx (key,seqno) values ('key1000', 1000);
> # count entries
> SELECT count(*) FROM snapshots.test_idx;
> 1000
> # restart service
> kill <cassandra-pid>
> cassandra -f
> # count entries
> SELECT count(*) FROM snapshots.test_idx;
> 0
> {code}
> I hope someone can point me to the obvious mistake I am doing :-)
> This happened to me using both Cassandra 3.9 and 3.11.0

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message