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

Clarify the 'Lock config server replica set secondary' section

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Done
    • Icon: Major - P3 Major - P3
    • mongodb-3.2
    • mongodb-3.2
    • manual
    • None

    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

            Unassigned Unassigned
            kaloian.manassiev@mongodb.com Kaloian Manassiev
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:
              7 years, 47 weeks ago