[SERVER-81025] Exclude change collections from dbHash validation Created: 13/Sep/23  Updated: 29/Oct/23  Resolved: 28/Sep/23

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

Type: Bug Priority: Major - P3
Reporter: Haley Connelly Assignee: Yujin Kang Park
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
related to SERVER-75440 Add separate check for preimage consi... Closed
related to SERVER-81485 More robust test coverage for change ... Closed
Assigned Teams:
Storage Execution EMEA
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Execution EMEA Team 2023-10-02
Participants:
Linked BF Score: 134

 Description   

When featureFlagUseUnreplicatedTruncatesForDeletions is enabled, change collection entries are removed via unreplicated truncates. This means the change collection entries of different nodes in a replica set can be truncated at different rates. 

It's not safe to check change collection entries through dbHash in the typical manner. Instead, a check similar the pre-image check added as part of SERVER-75440 should be added to guarantee the change entries are consistent.

 



 Comments   
Comment by Githook User [ 28/Sep/23 ]

Author:

{'name': 'Yu Jin Kang Park', 'email': 'yujin.kang@mongodb.com', 'username': 'ykangpark'}

Message: SERVER-81025 Ignore change_collection dbHash mismatch and add consistency checker
Branch: master
https://github.com/mongodb/mongo/commit/644e433cf72e834d1ac90069d79dc8626c499479

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