[DOCS-8860] EBS volumes should be initialised after creating from the snapshot before starting the {{mongod}} process Created: 26/Sep/16 Updated: 23/Jan/24 Resolved: 23/Jan/24 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | Atlas, ecosystem |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Ankur Raina (Inactive) | Assignee: | Unassigned |
| Resolution: | Gone away | Votes: | 0 |
| Labels: | request | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 2 weeks, 1 day ago |
| Description |
|
As per the AWS docs:
If the volumes are not initialised, it may take several minutes to several hours for the mongod instance to start. This generally affects MongoDB 3.2 with WiredTiger which samples the oplog while starting (see SERVER-19551). However, it should be better to have the volume initialised in all versions as the data anyways has to be read from disk and the process will be slow for uninitialised volumes. Information regarding this behaviour should be good to have in either of these MongoDB docs:
Related tickets: Help: https://jira.mongodb.org/browse/HELP-2705 |
| Comments |
| Comment by Emet Ozar [ 23/Jan/24 ] |
|
these pages don't exist anymore |
| Comment by Emily Hall [ 26/Sep/16 ] |
|
Assigning to jonathan.destefano for grooming. |
| Comment by Ankur Raina (Inactive) [ 26/Sep/16 ] |
|
I raised this by mistake in this project and was unable to move to DOCS. Please move if possible and also close DEPM-179 which got created as a clone of this ticket. I apologise for the trouble. |