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

Prefer the VectorClock's ConfigTime to configOpTime when querying config servers

    • Minor Change
    • Sharding 2020-09-07

      Currently, querying the config servers still uses configOpTime() for the readConcern afterOpTime. However, if there is an initialized value (ie. not kUninitialized) for the VectorClock's ConfigTime component (and FCV is initialised and indicates kVersion451 or later), then that should instead be used (with afterClusterTime, not afterOpTime). (For upgrade/downgrade purposes, if these conditions are not met, then the server should fall back to the existing behaviour of configOpTime() for afterOpTime.)

      configOpTime() is also used for the readPreference minOpTime (here and here). It's not clear what should be done about these (since configOpTime() is to eventually be replaced by ConfigTime), but SERVER-46499 should help guide this.

            Assignee:
            pierlauro.sciarelli@mongodb.com Pierlauro Sciarelli
            Reporter:
            kevin.pulo@mongodb.com Kevin Pulo
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: