[DOCS-4168] Description of STARTUP2 is misleading for initial syncs Created: 11/Oct/14 Updated: 16/Mar/15 Resolved: 13/Oct/14 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual |
| Affects Version/s: | None |
| Fix Version/s: | v1.3.12 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Cailin Nelson | Assignee: | Sam Kleinman (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 9 years, 18 weeks, 2 days ago |
| Description |
|
The documentation implies that this is always a short-lived state. However, if you are doing a new initial sync, the node is in STARTUP2 for the entire time that it takes to transfer the data and do the initial set of index builds. This can take many hours (or days). Thus, it seems misleading to say that: "Members are in the STARTUP2 state for a short period of time before entering the RECOVERING state. " http://docs.mongodb.org/manual/reference/replica-states/#replstate.STARTUP2 |
| Comments |
| Comment by Githook User [ 13/Oct/14 ] |
|
Author: {u'username': u'tychoish', u'name': u'Sam Kleinman', u'email': u'samk@10gen.com'}Message: |