Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-23315

Encapsulate _configOpTime

    • Type: Icon: Bug Bug
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 3.2.17
    • Component/s: Sharding
    • None
    • Sharding
    • ALL

      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.

            Assignee:
            backlog-server-sharding [DO NOT USE] Backlog - Sharding Team
            Reporter:
            misha.tyulenev@mongodb.com Misha Tyulenev (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: