Uploaded image for project: 'Documentation'
  1. Documentation
  2. DOCS-14300

Investigate changes in SERVER-54908: Shard servers with 4.9 binary and 4.4 FCV should be able to use secondaryDelaySecs

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Open
    • Priority: Major - P3
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: 4.9.0
    • Component/s: manual, Server
    • Labels:
      None
    • Last comment by Customer:
      true
    • Story Points:
      2
    • Sprint:
      ServerDocs2020: May18 - May25, ServerDocs2020: May25 - Jun1, ServerDocs2021: Jun1 - Jun8, ServerDocs2021: Jun8 - Jun15, ServerDocs2021: Jun15 - Jun22, ServerDocs2021: Jun22 - Jun29, ServerDocs2021: Jun29 - Jul6

      Description

      Description

      Downstream Change Summary

      We should document the manual downgrade procedure for a shard server binary that attempted to downgrade to 4.4 with the secondaryDelaySecs field still present. We point users to this link: http://www.mongodb.org/dochub/core/recover-replica-set-from-invalid-config so it should be updated accordingly.

      The test goes through the following procedure:
      1. Start up a shard server process with MDB 4.9 / FCV (featureCompatibilityVersion) 4.4 (note: new shard servers will default to the last-LTS FCV until they are added to a sharded cluster via addShard)
      2. Call rs.init() with secondaryDelaySecs in the replica set config.
      3. Downgrade shard binary to MDB 4.4 / FCV 4.4 by stopping the shard server and restarting with "binary: 4.4". During this step, the shard server will refuse to start up because it sees an unrecognized field (secondaryDelaySecs). In order for the user to get out of this situation, they'll have to do the following:

      • Restart shard with MDB 4.9 ("binary: 4.9") / FCV 4.4.
      • Reconfig to change 'secondaryDelaySecs' to 'slaveDelay'.
      • Downgrade shard binary to MDB 4.4 / FCV 4.4 by restarting shard with "binary: 4.4". The shard server should successfully start up.

      Note: This is specific to downgrading to 4.4 from 5.0.

      Description of Linked Ticket

      New 4.9 shard servers use the default 4.4 FCV, and therefore reject secondaryDelaySecs, until either:

      • they are added to a cluster with 4.9 FCV (via addShard)
      • they are added to a cluster with 4.4 FCV and the FCV is then set to 4.9 for the entire cluster via mongos

      During this period, we should allow shard servers to initialize with secondaryDelaySecs since they are using the 4.9 binary.

      Scope of changes

      Impact to Other Docs

      MVP (Work and Date)

      Resources (Scope or Design Docs, Invision, etc.)

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              backlog-server-pm Backlog - Core Eng Program Management Team
              Participants:
              Last commenter:
              Jeffrey Allen Jeffrey Allen
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Due:
                Created:
                Updated:
                Days since reply:
                37 weeks ago
                Date of 1st Reply: