[
https://issues.apache.org/jira/browse/CASSANDRA-15538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17214614#comment-17214614
]
Josh McKenzie commented on CASSANDRA-15538:
-------------------------------------------
So to summarize a checkpoint of where we are:
# The scope on this ticket as described is quite large and untargated
# The historical pain in the StorageEngine seems to center around LegacyLayout
stuff w/CASSANDRA-8099
# We believe randomized schema testing and query combinations are one of our
best ways to increase confidence in this space
# Harry is well suited to this work
# Harry isn't quite ready for this in terms of us coupling the 4.0 GA with this
# Orthogonally, reverse queries and range tombstones have historically been a
little sketchy
1-5 imply to me a subsequent iterative approach to improving our coverage there
as we don't necessarily have reason to believe there's major regression between
3.0 and 4.0, or 3.11 and 4.0, in this area of the codebase. There's also been a
significant raft of both real workload and real schema testing done against
mixed version clusters straddling 2.1 and 3.0 so there's an argument we should
be reasonably confident in the post CASSANDRA-8099 mixed version state.
So an option here would be to do the following (trying to keep things moving
along; not married to this):
# Pre 4.0: Flesh out more testing for reverse queries and range tombstones
# Pre 4.0: Selectively take a look at code coverage analysis for unit testing
in this domain and look for obvious gaps and beef up unit testing there
# Post 4.0 (4.0.x): incrementally work to wire up Harry, Fallout, generative
cassandra-diff framework testing w/user schemas (coming soon)
[~ifesdjeen] / [~aleksey]: Thoughts on ^?
> 4.0 quality testing: Local Read/Write Path: Other Areas
> -------------------------------------------------------
>
> Key: CASSANDRA-15538
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15538
> Project: Cassandra
> Issue Type: Task
> Components: Test/dtest/java, Test/dtest/python
> Reporter: Josh McKenzie
> Priority: Normal
> Fix For: 4.0-beta
>
>
> Reference [doc from
> NGCC|https://docs.google.com/document/d/1uhUOp7wpE9ZXNDgxoCZHejHt5SO4Qw1dArZqqsJccyQ/edit#]
> for context.
> *Shepherd: Aleksey Yeschenko*
> Testing in this area refers to the local read/write path (StorageProxy,
> ColumnFamilyStore, Memtable, SSTable reading/writing, etc). We are still
> finding numerous bugs and issues with the 3.0 storage engine rewrite
> (CASSANDRA-8099). For 4.0 we want to ensure that we thoroughly cover the
> local read/write path with techniques such as property-based testing, fuzzing
> ([example|http://cassandra.apache.org/blog/2018/10/17/finding_bugs_with_property_based_testing.html]),
> and a source audit.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
