[
https://issues.apache.org/jira/browse/CASSANDRA-14013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17648152#comment-17648152
]
Paulo Motta commented on CASSANDRA-14013:
-----------------------------------------
bq. If you scroll up enough, there is my original PR which was also trying to
base the solution to this problem on regexp (1) but then we kind of abandoned
that in favor of more concise and "less invasive" patch.
Sorry, I missed that.
bq. If yes, why do you want to have simpler in 4.0 and 4.1 and this new stuff
in trunk only? Is not it better to just have one approach committed everywhere?
The simpler fix is less invasive so less riskier for released versions, we
probably will no longer touch this code. The regex fix changes the way
directories are parsed but is more robust and future-proof so we would adopt
that moving forward in trunk, at least until we have the proper fix of encoding
keyspace/table/index info in the sstable metadata.
bq. Also, SSTableLoaderTest#testLoadingBackupsTable is failing for me locally
while testLoadingSnapshotsTable is not. Maybe your patch is not covering
something?
I haven't checked tests other than \{{DescriptorTest}}, I'll take a look and
submit a full CI run.
> 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, Local/Snapshots
> Reporter: Gregor Uhlenheuer
> Assignee: Stefan Miklosovic
> Priority: Normal
> Fix For: 4.0.x, 4.1.x, 4.x
>
> 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]
