[SERVER-62048] Test command relation invariants for change streams Created: 14/Dec/21  Updated: 06/Dec/22

Status: Backlog
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Nikita Lapkov (Inactive) Assignee: Backlog - Query Execution
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-61903 Add resmoke hook to test general trut... Closed
Assigned Teams:
Query Execution
Participants:

 Description   

Add a new resmoke hook, which opens the change stream at the end of the test and checks general truths. This way, we are relying on the diversity of our tests to provide interesting sequences of commands issued to construct various edge case scenarios. This could potentially prevent bugs like SERVER-61026 from happening.

An example of an illegal sequence of events such a hook could potentially detect: “create (shard A), shardCollection (shard A), drop (shard A), create (shard A), insert (shard A), drop (shard B)”. Note how create and insert events from shard A happen before the drop event from shard B.


Generated at Thu Feb 08 05:54:01 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.