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

Update sharding architecture guide to include VectorClock details

    XMLWordPrintableJSON

Details

    • Icon: Improvement Improvement
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 4.9.0
    • None
    • Sharding
    • None
    • Fully Compatible
    • Sharding 2020-09-21, Sharding 2020-10-05, Sharding 2020-10-19

    Description

      Potential template:

      The sharding vector clock (config OpTime, logical clock, databaseVersion, collectionVersion, shardVersion)

      • Should include
        • What is the type of each of these versions
        • How is each version derived (e.g., shardVersion is the max across all chunks owned by the shard, etc)
        • What are the processes, at a high level, which advance each version (e.g. writes to the config server advance the config OpTime)
        • At a conceptual level, how are config OpTime and logical time gossiped?
        • Why is there a config OpTime separate from clusterTime?
      • Code references
        • Where config OpTime is attached in requests and responses
        • Where config OpTime is stored in memory on each node
        • Where clusterTime is attached in requests and responses
        • Where clusterTime is stored in memory on each node
        • An example of where shardVersion and databaseVersion are attached in egress requests and parsed in ingress requests
        • Where collectionVersion is used to do an incremental refresh

      Attachments

        Activity

          People

            kevin.pulo@mongodb.com Kevin Pulo
            kevin.pulo@mongodb.com Kevin Pulo
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: