[SERVER-71442] Avoid testing pre-images in replication inital sync fuzzer tests Created: 17/Nov/22  Updated: 28/Nov/22  Resolved: 28/Nov/22

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

Type: Improvement Priority: Major - P3
Reporter: Denis Grebennicov Assignee: Denis Grebennicov
Resolution: Duplicate Votes: 0
Labels: greenerbuild
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Sprint: QE 2022-11-28, QE 2022-12-12
Participants:

 Description   

While investigating BF-26956 we noticed that pre-images replication is tested in initial sync fuzzer tests. This is not desirable as according to the design of the pre-images, they are not replicated during the initial sync process, causing fuzzer test failure.

Pre-images are not added to the fuzzer grammar, however, fuzzer may still generate tests that involve creation of the collections with pre-images being enabled.

We would want to avoid generating and investigating similar BFs in the future. In order to do so we could do:

  • set expiration duration to minimum amount (1 second) and ensure that pre-images are deleted after running the test, prior the initial sync process
  • adjust the fuzzer code to not generate code related to changeStream pit pre-images (e.g. no create/collMod support for changeStreamPreAndPostImages: enabled)
  • add pre-images collection UUID into the ignoreUUIDs of db-hash in run_initial_sync_node_validation.js
  • other options (or do nothing as this issue is pretty rare)

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