Page History

Correctness

Persistent Corruption / Loss

Corruption that persists, and may propagate across the cluster

Response Corruption / Loss

Corruption that does not propagate or persist, only results in a client receiving erroneous responses

Semantic Failure

The logical behaviour is either not to spec, or the spec is faulty/ambiguous

Consistency Failure

Apparently successful action, but with lower consistency than required

Test Failure

A test is broken - if this turns out to be a legitimate bug, it should transition to this category when it is the bug's category once diagnosed

Availability

Response Crash

An operation does not succeed/respond because of a crash while servicing it, without affecting process stability

Process Crash

An isolated exceptional state occurs that brings down the affected node

Cluster Crash

An A correlated exceptional state occurs across the cluster, bringing down a multiplicity of nodes

Unavailable

Apparently unavailable, when should be available

Degradation

Resource Management

Either a resource leak or overcommit

Slow Use Case

A specific use case with suboptimal characteristics that have not yet been accommodated

Performance Bug/Regression

Unintended performance behaviour, including e.g. exceptions stalling compactions

Other Exception

An exception is being thrown, that is not coinciding with another category of degradation

Security

Information Leakage

Privilege Escalation

Denial of Service