[SERVER-23315] Encapsulate _configOpTime Created: 23/Mar/16  Updated: 06/Dec/22  Resolved: 24/Oct/17

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

Type: Bug Priority: Major - P3
Reporter: Misha Tyulenev Assignee: [DO NOT USE] Backlog - Sharding Team
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-22611 ChunkManager refresh can occasionally... Closed
Assigned Teams:
Sharding
Operating System: ALL
Participants:

 Description   

The _configOpTime used in Database, Collection and Chunks metadata to ensure that DBConfig <= CollectionInfo <= ChunkManager configOpTime,
Sometimes the check for those invariants is too strong: e.g. https://github.com/mongodb/mongo/blob/13271aa2d75ff3c15444aad8b4e0d67837e113bc/src/mongo/s/config.cpp#L411-L421

configOpTime setting/getting and comparison responsibilities should be encapsulated in a new class for example that can be used as a base for DBConfig, CollectionInfo, ChunkManager.



 Comments   
Comment by Kaloian Manassiev [ 24/Oct/17 ]

After the changes done for SERVER-22611 in 3.4.4, these values no longer exist in the codebase.

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