[DOCS-5822] restore replica set has odd second step Created: 10/Jul/15 Updated: 11/Jan/17 Resolved: 11/Jul/15 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual |
| Affects Version/s: | None |
| Fix Version/s: | 01112017-cleanup |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Sam Kleinman (Inactive) | Assignee: | Kay Kim (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 8 years, 31 weeks, 4 days ago |
| Description |
|
http://docs.mongodb.org/manual/tutorial/restore-replica-set-from-backup/ The second step where you start the instance as a standalone and then shut it down doesn't seem to make a lot of sense. I think this is a vestigial artifact of a previous version where we had people do something to set minValid so that copying data files wouldn't trigger resyncs, but there may have been a regression. I think on the whole, the use of multiple sequences here is confusing, and we should try and reform this so that there's a single sequence of steps. |
| Comments |
| Comment by Githook User [ 11/Jul/15 ] |
|
Author: {u'username': u'kay-kim', u'name': u'kay', u'email': u'kay.kim@10gen.com'}Message: |
| Comment by Githook User [ 11/Jul/15 ] |
|
Author: {u'username': u'kay-kim', u'name': u'kay', u'email': u'kay.kim@10gen.com'}Message: |
| Comment by Githook User [ 11/Jul/15 ] |
|
Author: {u'username': u'kay-kim', u'name': u'kay', u'email': u'kay.kim@10gen.com'}Message: |