Details
-
Bug
-
Resolution: Done
-
Major - P3
-
None
-
None
-
*Location*: https://docs.mms.mongodb.com/tutorial/restore-replica-set/#run-the-seedsecondary-sh-script-on-the-primary
*User-Agent*: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:35.0) Gecko/20100101 Firefox/35.0
*Referrer*: https://github.com/10gen/training/pull/18
*Screen Resolution*: 2560 x 1440
*repo*: REPONAME
*source*: tutorial/restore-replica-set
*Location*: https://docs.mms.mongodb.com/tutorial/restore-replica-set/#run-the-seedsecondary-sh-script-on-the-primary *User-Agent*: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:35.0) Gecko/20100101 Firefox/35.0 *Referrer*: https://github.com/10gen/training/pull/18 *Screen Resolution*: 2560 x 1440 *repo*: REPONAME *source*: tutorial/restore-replica-set
Description
If the replica set is managed by an automation agent, these instructions won't work as written. The "db.shutdownServer()" will shut down the server, but the automation agent will bring it right back up again.
Ideally this will become moot if it becomes possible to automate the whole restore process, but in the mean time the instructions should probably mention that you have to shut down servers using the MMS console.