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

VectorClock's configTime can become greater than clusterTime after a signature failure

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Won't Do
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Sharding
    • None
    • Sharding EMEA
    • ALL
    • Sharding EMEA 2022-06-13, Sharding EMEA 2022-06-27

      If the key to sign the clusterTime was not available, VectorClock::SignedComponentFormat::out will not write it to the BSON builder and will return false. Then VectorClock::gossipOut may have built $configTime and $topologyTime, but not $clusterTime, and thus return false. Finally, VectorClockMetadataHook::writeRequestMetadata will write only $configTime and $topologyTime to the request. The receiving node will then possibly advance it's VectorClock::configTime but not the clusterTime. So configTime could become ahead of clusterTime.

            Assignee:
            backlog-server-sharding-emea [DO NOT USE] Backlog - Sharding EMEA
            Reporter:
            jordi.serra-torrens@mongodb.com Jordi Serra Torrens
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: