[
https://issues.apache.org/jira/browse/CASSANDRA-15537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Josh McKenzie updated CASSANDRA-15537:
--------------------------------------
Description:
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.
was:
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.
> 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
> 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: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
