Regression

Single-Server Regression

Used to check all the features work correctly after any changes.

Multi-Server Regression

Used to check important features behavior

  • on a real cluster (with different hardware, software, environment settings)
  • with plugins (eg. GridGain, SberEdition, etc).
CaseCovered by
control.sh

--activate: Done

--baseline: Done

--deactivate: Done

--tx:  Unable to render Jira issues macro, execution error.

--snapshot:

--restore:

Thin JDBC driver coverage

Unable to render Jira issues macro, execution error.

ODBC driver coverage
Metrics coverage
JMX coverage

Thin Client API coverage


Cellular affinity distribution is cellularDone

Checks

Integration Checks

Used to check integrations with other projects (eg. Zookeeper, Kafka, Spark, etc).

CaseCovered by


Rolling Upgrade Checks

Used to check migrations from one version/vendor to another.

CaseCovered by
Persistence based Rolling Upgrade
Thin client compatibility (backward and forward)

PoC Checks

Used to check some concepts or to automate MVP demonstration.

CaseCovered by
AnyCovered on demand

Consistency Checks

Used to check data consistency during the typical load.

CaseCovered by
AnyJepsen?

Fuzzy Checks

Used to check results correctness during mixed load.

CaseCovered by


Crash Recovery Checks

Used to check system behavior on crashes.

CaseCovered by
Latency degradation on Switch on node left/fail

PME:

PME-free: Done

Cellular:  Unable to render Jira issues macro, execution error.

Failure detection duration

TCPDiscovery:

Zookeeper:

Various rebalance modes (historical, regular, etc)
Cluster coordinator crash
Transaction coordinator crash

Benchmarks

Process Benchmarks

Used to check measure duration of important precesses (eg. PME, Snapshot, Rebalance, Node start, etc)

CaseCovered by
Rebalance duration
Snapshot duration

Profile Benchmarks

Used to check customer's profile performance on some environment.

CaseCovered by
AnyCovered on demand

Synthetic Benchmarks

Used to compare overall performance from version to version and from commit to commit

CaseCovered by
The operation's through/latencyYardstick
  • No labels