Use causal consistency in database_versioning_upgrade_downgrade.js test when reading from secondary after setFCV

XMLWordPrintableJSON

    • Fully Compatible
    • ALL
    • Sharding 2018-09-24
    • 29
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      The setFCV command returns after a majority of nodes have committed the write to the FCV document, so if a client gets success for setFCV and then does a read against a secondary, that secondary may not yet be in the new FCV.

              Assignee:
              Jack Mulrow
              Reporter:
              Esha Maharishi (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: