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

Fix ShardRegistry::Time definition

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 8.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • Fully Compatible
    • ALL
    • v8.0
    • CAR Team 2024-08-05, CAR Team 2024-08-19
    • 200

      Currently, the Time definition of the ShardRegistry has some flaws:

      • no total order: potential causal consistency breakage (timeInStore overwriting a newer topologyTime).
      • Null topologyTime cause the topologyTime component to be ignored. In the absence of forceReloads or rsmIncrements, the topologyTime in VectorClock never advances timeInStore.

      The Time definition should be reworked to address these issues.

            Assignee:
            yujin.kang@mongodb.com Yujin Kang Park
            Reporter:
            yujin.kang@mongodb.com Yujin Kang Park
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: