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

mongodump/mongoexport should issue its own lock command

    • Type: Icon: Bug Bug
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 1.4.0, 1.4.1, 1.4.2, 1.4.3, 1.4.4, 1.5.0, 1.5.1, 1.5.2, 1.5.3, 1.5.4, 1.5.5, 1.5.6, 1.5.7, 1.5.8, 1.6.0
    • Component/s: None
    • None
    • Environment:
      All environments
    • ALL

      Mongodump and mongoexport have two forms of operation. They either connect to a running mongod instance or they operate directly on a mongo data directory. What I learned recently from Kristinia's blog (http://www.snailinaturtleneck.com/blog/2010/07/26/mongodb-backups-corn-on-the-cob-in-10-minutes/) was that it does not lock the database before dumping for ensure consistency.

      There should be a switch to opt into a locking the database, I propose l/-lockDatabases.This will simplify backup scripts.

            Assignee:
            eliot Eliot Horowitz (Inactive)
            Reporter:
            zippy1981 Justin Dearing
            Votes:
            3 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: