[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: |
|
||||||||
| Assigned Teams: |
Sharding
|
||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
The _configOpTime used in Database, Collection and Chunks metadata to ensure that DBConfig <= CollectionInfo <= ChunkManager configOpTime, 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 |