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

Clarify the 'Lock config server replica set secondary' section

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Done
    • Affects Version/s: mongodb-3.2
    • Fix Version/s: mongodb-3.2
    • Component/s: manual
    • Labels:
      None
    • # Replies:
      2
    • Last comment by Customer:
      true

      Description

      The documentation page for backing up a sharded cluster contains a section on how to lock config server replicaset's secondary in order to get a consistent metadata snapshot.

      The section requests to search for a 'moveChunk.commit' message, which will work most of the time, but in the case of failed migrations it might not.

      A more appropriate instructions would be to run the same query:

      use config;
      db.changelog.find({what:/^moveChunk/}).sort({time:-1}).next()
      

      And make sure that the last moveChunk.start entry has a corresponding moveChunk.commit or moveChunk.from entry, which would indicate that the latest migration has completed (whether successfully or not).

        Attachments

          Activity

            People

            Assignee:
            Unassigned
            Reporter:
            kaloian.manassiev Kaloian Manassiev
            Participants:
            Last commenter:
            Jonathan Dahl
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

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