[ 
https://issues.apache.org/jira/browse/CASSANDRA-15537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17204178#comment-17204178
 ] 

Yifan Cai commented on CASSANDRA-15537:
---------------------------------------

Hi Paulo,

Dozens of clusters so far have passed the diff test that compares between its 
current build and the latest 4.0 build. The number of clusters being tested is 
increasing each week. The tested clusters have the data size ranging from 
gigabytes to 10s of TB.

The success criteria for a diff test is that 100% of data from user tables 
matches between the 2 testing clusters. 

Several issues have been resolved, and tool improvements has been made during 
this on-going diff exercise. The tickets are:

Issues
 * CASSANDRA-15945
 * CASSANDRA-15905
 * CASSANDRA-15857
 * CASSANDRA-15514

Tool improvements
 * CASSANDRA-16125
 * CASSANDRA-16065
 * CASSANDRA-15953
 * CASSANDRA-15807
 * CASSANDRA-15722
 * CASSANDRA-15658

> 4.0 quality testing: Local Read/Write Path: Upgrade and Diff Test
> -----------------------------------------------------------------
>
>                 Key: CASSANDRA-15537
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-15537
>             Project: Cassandra
>          Issue Type: Task
>          Components: Test/dtest/java, Test/dtest/python
>            Reporter: Josh McKenzie
>            Assignee: Yifan Cai
>            Priority: Normal
>             Fix For: 4.0-beta
>
>
> Reference [doc from 
> NGCC|https://docs.google.com/document/d/1uhUOp7wpE9ZXNDgxoCZHejHt5SO4Qw1dArZqqsJccyQ/edit#]
>  for context.
> Execution of upgrade and diff tests via cassandra-diff have proven to be one 
> of the most effective approaches toward identifying issues with the local 
> read/write path. These include instances of data loss, data corruption, data 
> resurrection, incorrect responses to queries, incomplete responses, and 
> others. Upgrade and diff tests can be executed concurrent with fault 
> injection (such as host or network failure); as well as during mixed-version 
> scenarios (such as upgrading half of the instances in a cluster, and running 
> upgradesstables on only half of the upgraded instances).
> Upgrade and diff tests are expected to continue through the release cycle, 
> and are a great way for contributors to gain confidence in the correctness of 
> the database under their own workloads.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to