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

shards should not gossip $logicalTime and operationTime if FCV is set to 3.4

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 3.5.10
    • None
    • Sharding
    • None
    • Fully Compatible
    • Sharding 2017-07-10

    Description

      Similar to mongos in SERVER-29652, shards and configs should not gossip $logicalTime if FCV is set to 3.4.
      While its unlikely that client will connect directly we should avoid the scenario when the afterCLusterTime clause is rejected but operationTime is still returned because its hard to address on the client side.

      In mongod the FCV is available hence the implementation is the following
      1. add a check that FCV == 36 in https://github.com/mongodb/mongo/blob/master/src/mongo/db/service_entry_point_mongod.cpp#L484
      so the operationTime will be added only in 36 mongod for sharded and standalone RS

      2. add a check that FCV == 36 in
      https://github.com/mongodb/mongo/blob/master/src/mongo/db/service_entry_point_mongod.cpp#L257-L268
      so the operationTime will be added only in 36 mongod for sharded and standalone RS

      Attachments

        Activity

          People

            jack.mulrow@mongodb.com Jack Mulrow
            misha.tyulenev@mongodb.com Misha Tyulenev
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: