[
https://issues.apache.org/jira/browse/CASSANDRA-15538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17204048#comment-17204048
]
Sylvain Lebresne commented on CASSANDRA-15538:
----------------------------------------------
No, I haven't really started anything on this issue, and I don't plan to in the
near term, so I unassigned myself. I should have done it sooner, my bad.
I did spent a few cycles some time ago thinking about what could be done
concretely here and I'll share my "reflections" in case that's useful. That
said, in general, the scope here was a bit fuzzy to me.
First, if you look at (true) unit testing for the classes that constitute the
read/write path, there isn't much. So I suppose one could try to cover that
somewhat, but the work to make a dent there is huge, and I'm not sure the value
is that great since those path are mostly covered, but by
"integration/functional" tests. But this doesn't make is super clear to me if
specific area are more in need of additional testing than others.
Then the description mentions "numerous bugs and issues with the 3.0 storage
engine rewrite", so I looked at the list of "serious bugs" that was shared on
the mailing list (by [~kohlisankalp] I believe; too lazy to dig the link right
now). From looking at that, the biggest bucket I saw for "storage engine
rewrite" related bugs was with 'legacy layout conversions/handling'. And that
was clearly under-tested, but it's also gone in 4.0. From memory, there were
also 2-3 read-repair related bugs, but we have CASSANDRA-15977. Nothing else
struck me as pointing to a specific area to focus one.
Those aside and fwiw, I've a feeling that things like reverse queries and range
tombstones may be 2 features that aren't as well tested as they could, but it's
more an impression of mine than hard data.
Short of focusing on some specific area, the "read/write path" is a big place
and the space to explore is kinda big. So I feel the biggest value would be to
start exploring more of that space through randomized testing, specifically
randomizing queries and/or schema. Presumably, that's what
[Harry|https://issues.apache.org/jira/browse/CASSANDRA-15348] is for (though I
haven't really checked it as of yet, so I don't know how capable it is for
this). So if it was me, I'd look in this direction. But again, I don't have
plans to at the moment due to other priorities.
> 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]
