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

coll_epoch_test1.js does not wait for the config server to replicate after dropping collections.

    • Fully Compatible
    • ALL
    • v4.0, v3.6, v3.4
    • Sharding 2018-11-19
    • 0

      When using a mongos that can have a stale afterOpTime (not using it to communicate with other nodes), it is crucial that we guarantee that the config server is always fully replicated. The afterOpTime is usually gossiped between the mongos and other nodes, so that any majority read request will have a certain minimum time to read at.

      Failing to replicate in lieu of having an updated mongos afterOpTime can allow the mongos to read from a minority config server node that has an out-of-date majority commit point.

            esha.maharishi@mongodb.com Esha Maharishi (Inactive)
            blake.oler@mongodb.com Blake Oler
            0 Vote for this issue
            3 Start watching this issue