-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Cluster Scalability
-
Cluster Scalability Priorities
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Currently whenever a new oplog entry type is introduced, the engineers who introduced the new oplog entry type need to remember to test the new oplog type with resharding.
We should add a test that:
- Runs an engineer written workload
- Takes the list of all oplog types from the IDL file
- Asserts that the oplog entry type was generated by the workload written by the engineer
When new oplog entry types are added, the test will fail and so engineers will remember to add testing for their oplog entry type to the workload.
Ideally the test would look at all the oplog entry types from the IDL file and figure out how to test them. But that's hard because it's not obvious what commands to run on the server to generate a particular oplog entry type.
- is related to
-
SERVER-128360 Test that every oplog entry type has been tested with recoverFromOplogAsStandalone
-
- Backlog
-