Roy Dahan

The direction @yarongilor is checking at the moment is the fact that this keyspace was created when the cluster was in mixed mode (2 nodes upgraded, 2 haven't). @asias is...

@yarongilor did you proved that when running the s-b command that creates the schema before the upgrade, the issue doesn't reproduce? If so, please provide a reproducer, should be very...

@fgelcer please update here with your findings. AFAIU your changes proved that it related to when we create the schema for scylla-bench. Do you have a short and easy reproducer...

@eliransin will someone look at it? I'm setting the high lable since otherwise no one will ever fix it. And if no one is going to fix it, we can...

According to the original description, it happened on 2022.2.0~rc1-20220902.a9bc6d191031 which is equivalent 5.1

@soyacz can you please compare the code of the specific test we run to this test in dtest (should be exactly same): https://jenkins.scylladb.com/view/scylla-5.1/job/scylla-5.1/job/dtest-daily-release/10/testReport/cql_additional_tests/TestCQL/Run_Dtest_Parallel_Cloud_Machines___FullDtest___full_split000___test_dense_cf/ (Maybe there was a fix / change...

You can also check if it's related to upgrade, by adding this test as a step to the upgrade_test we have in dtest (in the same places we have the...

@soyacz can you please try to reproduce it in dtest?

It reproduced in at least one run out of 2 (the second one is less clear). @ShlomiBalalis please add details or a live cluster.

@soyacz we need to catch it live or set it to kill it with SIGABRT so it'll produce a coredump we can attach to the issue. If we can't produce...