Open bhalevy opened 1 year ago
https://github.com/scylladb/scylladb/pull/15820 changes this area too so this can be fixed after the former is merged (or in the same patchset)
Cc @denesb
https://github.com/scylladb/scylladb/pull/15820 was merged, so this issue can be worked on
@bhalevy , why did you label it 'ci stability'? seems like a bug/required change in the code
@bhalevy , why did you label it 'ci stability'? seems like a bug/required change in the code
it was labeled as such since it was hit in dtest. being a bug that needs fixing is orthogonal to ci stability, isn't it?
@bhalevy , why did you label it 'ci stability'? seems like a bug/required change in the code
it was labeled as such since it was hit in dtest. being a bug that needs fixing is orthogonal to ci stability, isn't it?
yes, I didnt notice that ci stability is only a symptom label.
There is nothing to prevent keyspaces or tables to be dropped during flush and returning
no_such_column_family
orno_such_keyspace
is futile since the end result if the table was dropped right after a successful flush is the same and the flushed sstables would be removed anyhow.This is causing for example the following dtest failure: https://jenkins.scylladb.com/view/master/job/scylla-master/job/dtest-release/420/testReport/materialized_views_test/TestMaterializedViews/Run_Dtest_Parallel_Cloud_Machines___FullDtest___full_split008___test_multi_mvs_on_different_base_tables/