You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Ke Han (Jira)" <ji...@apache.org> on 2022/12/25 23:15:00 UTC
[jira] [Commented] (CASSANDRA-18091) Column update lost after a full stop upgrade from 4.0.7 to 4.1.0
[ https://issues.apache.org/jira/browse/CASSANDRA-18091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17651896#comment-17651896 ]
Ke Han commented on CASSANDRA-18091:
------------------------------------
I have added a script to reproduce this bug easily.
Clone this [repo|[https://github.com/hanke580/cass_18091],] enter the run/ folder and execute ./run.sh
{code:java}
git clone --recursive git@github.com:hanke580/cass_18091.git
cd cass_18091/run
./run.sh{code}
This script automatically reproduces the bug within ~20mins.
> Column update lost after a full stop upgrade from 4.0.7 to 4.1.0
> ----------------------------------------------------------------
>
> Key: CASSANDRA-18091
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18091
> Project: Cassandra
> Issue Type: Bug
> Reporter: Ke Han
> Priority: Normal
>
> When we performed a full-stop upgrade from release 4.0.7 to 4.1.0, we executed the same read command before and after the upgrade and found that some column updates were lost after the upgrade.
> This inconsistency is likely related to timing and cannot be reproduced deterministically. Though it's non-deterministic, this failure *happens reliably* *once every ten times* when executing the following command sequence.
> h2. Steps to reproduce
> 1. Set up a 4.0.7 3-node cluster. (N0: seed node, N1, N2). Default configurations, set num_tokens to 256.
> 2. Execute the following cqlsh command at N0
> (The test commands use random parameters because it is generated by our testing tool)
> {code:java}
> CREATE KEYSPACE uuid5f86250110a247d48c481c5579cb2ea1 WITH REPLICATION = { 'class' : 'SimpleStrategy', 'replication_factor' : 1 };
> CREATE TABLE uuid5f86250110a247d48c481c5579cb2ea1.kattmG (kattmG TEXT,VldG TEXT,Ajqm TEXT,lTQSQ INT,EVzlSKrbkUGyhJshH TEXT, PRIMARY KEY (lTQSQ ));
> DELETE FROM uuid5f86250110a247d48c481c5579cb2ea1.kattmG WHERE lTQSQ = 2;
> ALTER TABLE uuid5f86250110a247d48c481c5579cb2ea1.kattmG DROP kattmG ;
> INSERT INTO uuid5f86250110a247d48c481c5579cb2ea1.kattmG (Ajqm, EVzlSKrbkUGyhJshH, lTQSQ) VALUES ('nZJzNjYnXOwPLpVoFSVwxcvznsDFBYqmlprrVXYJQLzYvYkrmfEsiuAcCtggypnxIkIevRHyPQGOWrIZNObJ','RaAhbVKUQzgJaupaupKPVnNLLYDaZEaMyFteVwhLePqZwikuBEsVDxTuTqBfkFYmeMMsOFXjVkObZduPfAFsLzuYlrgpYsPPxDNQCRzzPaEdWHARnnWbAFAUUnbYnvEESeHDRHSkEhSnoREprrHWasYLMSocIYiMGQXjzsaKptqbtPgrztIdpQLgDAZOPfhJIblmwTFAWiFbzrbTkFwJGP',1693380861);
> DELETE FROM uuid5f86250110a247d48c481c5579cb2ea1.kattmG WHERE lTQSQ = 1693380861;
> INSERT INTO uuid5f86250110a247d48c481c5579cb2ea1.kattmG (lTQSQ) VALUES (2);
> ALTER TABLE uuid5f86250110a247d48c481c5579cb2ea1.kattmG DROP VldG ;
> INSERT INTO uuid5f86250110a247d48c481c5579cb2ea1.kattmG (lTQSQ) VALUES (1693380861);
> INSERT INTO uuid5f86250110a247d48c481c5579cb2ea1.kattmG (Ajqm, lTQSQ) VALUES ('ldrsHa',1693380861);
> ALTER TABLE uuid5f86250110a247d48c481c5579cb2ea1.kattmG DROP Ajqm ;{code}
> 3. Execute a SELECT command at N0, and get results
> {code:java}
> SELECT lTQSQ FROM uuid5f86250110a247d48c481c5579cb2ea1.kattmG;
> ltqsq
> ------------
> 1693380861
> 2
> (2 rows){code}
> 4. Perform a full-stop upgrade. (Set num_tokens to 256)
> 1. Drain N0, stop N0.
> 2. Drain N1, stop N1.
> 3. Drain N2, stop N2.
> 4. Start up N0.
> 5. Start up N1.
> 6. Start up N2.
> 5. Execute the same SELECT command at N0, and get results
> {code:java}
> SELECT lTQSQ FROM uuid5f86250110a247d48c481c5579cb2ea1.kattmG;
> ltqsq
> -------
> 2
> (1 rows){code}
> Or
> {code:java}
> SELECT lTQSQ FROM uuid5f86250110a247d48c481c5579cb2ea1.kattmG;
> ltqsq
> -------
> (0 rows){code}
>
> The new result is inconsistent with the old version's result. The insert update is lost.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org