[ 
https://issues.apache.org/jira/browse/CASSANDRA-14013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Paulo Motta updated CASSANDRA-14013:
------------------------------------
          Fix Version/s: 4.0.8
                         4.1.1
                         4.2
                             (was: 4.x)
                             (was: 4.0.x)
                             (was: 4.1.x)
          Since Version: 3.0.0
    Source Control Link: 
https://github.com/apache/cassandra/commit/6e6846892a5d7ec2feaf2c35d380ed5975d09517
             Resolution: Fixed
                 Status: Resolved  (was: Ready to Commit)

Committed asĀ 
[6e6846892a5d7ec2feaf2c35d380ed5975d09517|https://github.com/apache/cassandra/commit/6e6846892a5d7ec2feaf2c35d380ed5975d09517]
 to {{cassandra-4.0}} and merged to 
[cassandra-4.1|https://github.com/apache/cassandra/commit/c9968a8e95253a23846be1b5f502773a1eeea48d]
 and 
[trunk|https://github.com/apache/cassandra/commit/6501f576e7c663d285a4db207e6b3dc7f887e8f4]
 (regex-based version).



Created CASSANDRA-18168 to serialize keyspace/table metadata on 
{{StatsMetadata}} component.

> Keyspace named "snapshots" is empty after service restart
> ---------------------------------------------------------
>
>                 Key: CASSANDRA-14013
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-14013
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Legacy/Core, Local/Snapshots
>            Reporter: Gregor Uhlenheuer
>            Assignee: Stefan Miklosovic
>            Priority: Normal
>             Fix For: 4.0.8, 4.1.1, 4.2
>
>          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.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to