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

Test that safe secondary reads is inactive until 3.6 feature compatibility version is set

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 3.6.0-rc0
    • Affects Version/s: None
    • Component/s: Sharding
    • None
    • Fully Compatible
    • Sharding 2017-10-02

      Test that a 3.4 feature compatibility version mixed shard replica sets behave as v3.4 servers, then smoothly transition to 3.6 feature compatibility operation. In 3.4 fcv, orphans should be readable on secondaries. Once 3.6 fcv is set, secondaries should not need to refresh remotely, but should just start working.

      The profiler might be useful for testing: https://github.com/mongodb/mongo/blob/master/jstests/libs/profiler.js

            Assignee:
            dianna.hohensee@mongodb.com Dianna Hohensee (Inactive)
            Reporter:
            dianna.hohensee@mongodb.com Dianna Hohensee (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: