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

commitMovePrimary concurrent with setFCV may write incorrect metadata

    XMLWordPrintable

    Details

    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Sprint:
      Sharding EMEA 2021-05-03

      Description

      When upgrading fcv to 5.0, the configsvr will patch-up the sharding metadata. In particular, it will set a 'timestamp' on the config.databases documents.

      If this patch up happens concurrently with a commitMovePrimary, it could happen that commitMovePrimary reads the current config.databases entry (without timestamp), then the setFCV thread patches up the entry so it has a timestamp, and finally, the commitMovePrimary writes the updates database version without a timestamp.

        Attachments

          Activity

            People

            Assignee:
            antonio.fuschetto Antonio Fuschetto
            Reporter:
            jordi.serra-torrens Jordi Serra Torrens
            Participants:
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: