[ 
https://issues.apache.org/jira/browse/CASSANDRA-14013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17223066#comment-17223066
 ] 

Stefan Miklosovic edited comment on CASSANDRA-14013 at 10/29/20, 5:18 PM:
--------------------------------------------------------------------------

[~mck]

I wanted to approach this more robustly and I think I am getting there but for 
some strange reason the bunch of tests are failing. I am not sure what is wrong 
here as they do not seem to fail locally.

The current solution does not count on the fact that for example there might be 
also a snapshot / table called "snapshot" as well as "backups" for example - 
same for indexes and indexes in backups and snapshots. There might be also a 
snapshot called "snapshot" for a keyspace which is called "snapshot" and table 
which is called "snapshot" too and so on ...

That code solves all these issues.

The fact that tests were failing was that tests do not use data locations from 
descriptor but sstables are somewhere in /tmp/ which furtherly complicates 
things.

PR: [https://github.com/apache/cassandra/pull/798] (there is link to build too).

 

EDIT: some of them do fail locally, I am on it.


was (Author: stefan.miklosovic):
[~mck]

I wanted to approach this more robustly and I think I am getting there but for 
some strange reason the bunch of tests are failing. I am not sure what is wrong 
here as they do not seem to fail locally.

The current solution does not count on the fact that for example there might be 
also a snapshot / table called "snapshot" as well as "backups" for example - 
same for indexes and indexes in backups and snapshots. There might be also a 
snapshot called "snapshot" for a keyspace which is called "snapshot" and table 
which is called "snapshot" too and so on ...

That code solves all these issues.

The fact that tests were failing was that tests do not use data locations from 
descriptor but sstables are somewhere in /tmp/ which furtherly complicates 
things.

 

PR: [https://github.com/apache/cassandra/pull/798] (there is link to build too).

> Data loss in snapshots keyspace after service restart
> -----------------------------------------------------
>
>                 Key: CASSANDRA-14013
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-14013
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Legacy/Core
>            Reporter: Gregor Uhlenheuer
>            Assignee: Stefan Miklosovic
>            Priority: Normal
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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': 1};
> # 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
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

Reply via email to