-
Type:
Sub-task
-
Status: Resolved (View Workflow)
-
Priority:
Minor
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: None
-
Labels:
-
Sprint:K Sprint #1 - Platform, K Sprint #2 - Platform, K Sprint #3 - Platform
Transaction test applications are currently not suitable for testing atomicity/isolation. This can be easily done for strict atomicity/isolation by simply testing that a set of values represent a single transaction. For example, run three concurrent transactions setting three different values on n keys, and run concurrent transactions reading those keys and verifying that all keys have the same value. Retry transactions until they're successful. That ensures that the read transactions are isolated from write transactions and that writes within transactions are atomic.