[
https://issues.apache.org/jira/browse/CASSANDRA-15538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17206169#comment-17206169
]
Josh McKenzie commented on CASSANDRA-15538:
-------------------------------------------
{quote}bq. Having it run 24/7 on as large a cluster of boxes as possible,
reporting and collecting invariant failures
{quote}
Indeed. The example yaml in the repo is a 2 hour test with a random schema; is
there an example or could the codebase be augmented with a more robust schema
intended to be run for a longer period of time for people to base subsequent
work off?
Given how nascent the Harry project is + the lack of examples like that (no
judgement; new code is new code), I'm wary of us establishing a release
dependency between Harry being wired into our "official" CI/CD checklist
pipeline vs. having built our confidence in this release with the dirtier, more
disappointing "tested X schemas with cassandra-diff and FQLTool and fixed
defects we reproduced with Harry" and having an orthogonal task of wiring up
24/7 long-running soaks using Harry and Fallout as we move forward during the
4.0.1 etc time frame.
You certainly have more understanding re: the proximity of Harry's current
state to "is ready to be wired into our CI/CD and appropriate to block the
release on" [~aleksey] and/or [~ifesdjeen] - what do you guys think?
> 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, 4.0-triage
>
>
> 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: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
