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

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

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Blocked
    • Priority: Major - P3
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: Backlog
    • Component/s: Sharding
    • Labels:
    • Operating System:
      ALL

      Description

      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.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              backlog-server-sharding-nyc Backlog - Sharding NYC
              Reporter:
              jordi.serra-torrens Jordi Serra Torrens
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated: