https://jira.mongodb.org/browse/BF-34441 was caused due to background validation seeing back in time to an earlier checkpoint timestamp when mixed schema data had not yet been deleted, but using a current timeseriesBucketsMayHaveMixedSchemaData flag which was set to false. We need to add an fsync to protect against this.
- related to
-
SERVER-104757 Remove unnecessary fsync from timeseries mixed schema bucket tests
-
- Closed
-