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

Missing step to remove minOpTimeRecovery document during shared cluster restore

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Critical - P2
    • Resolution: Duplicate
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Last comment by Customer:
      true

      Description

      Description

      https://docs.mongodb.com/manual/tutorial/restore-sharded-cluster/

      Prior to this step on the shards, this step is missing:

      Remove the

      {"_id": "minOpTimeRecovery"}

      from the admin.system.version collection

      That document contains the minimum timestamp and election term for inclusion in queries to the CSRS. If the original cluster's CSRS experienced elections, the election term will be > 1 in that document. For example:

      { "_id" : "minOpTimeRecovery", "configsvrConnectionString" : "configRepl/localhost:39008,localhost:39009,localhost:39010", "minOpTime" : { "ts" : Timestamp(1547112229, 5), "t" : NumberLong(2) }, "minOpTimeUpdaters" : 0, "shardName" : "shard01" }
      

      Election term is value of t here:

      "t" : NumberLong(2) 
      

      Meanwhile, the newly restored CSRS will start out with election term = 1. If the document is not removed and the term > 1 in that document, it will result in unsatisfiable queries to the CSRS (since the CSRS term will never match the query term). This leaves the restored cluster in a degraded state.

      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:
              eric.sommer Eric Sommer
              Participants:
              Last commenter:
              Ravind Kumar Ravind Kumar (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Days since reply:
                2 years, 41 weeks, 4 days ago
                Date of 1st Reply: