[DOCS-12807] Using a snapshot restore from AWS EBS can see the oplog sampling performance significantly impacted Created: 17/Jun/19  Updated: 30/Oct/23

Status: Closed
Project: Documentation
Component/s: Server
Affects Version/s: None
Fix Version/s: Server_Docs_20231030

Type: Improvement Priority: Minor - P4
Reporter: Marco Bonezzi Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-27036 WT takes longer to start than MMAPv1 ... Closed
is related to SERVER-41790 Report progress during oplog sampling... Closed
Participants:
Days since reply: 1 year, 14 weeks, 2 days ago
Epic Link: DOCSP-1769
Story Points: 0.2

 Description   

Description

In certain situations (using EBS snapshot + large oplog), oplog sampling can take significantly longer because of data being loaded from S3 in AWS.

While this is due to AWS behaviour, it would be great to highlight in our docs the way an EBS snapshot will perform before being warm up and how this can affect the oplog sampling part of the mongod startup.

Scope of changes

  • This will likely need a section in the Production Notes, and possibly in our backup/restore docs

    Impact to Other Docs

  • Possible impact to ops/cloud manager snapshots on S3 buckets?

    MVP (Work and Date)

    Resources (Scope or Design Docs, Invision, etc.)



 Comments   
Comment by Education Bot [ 31/Oct/22 ]

Hello! This ticket has been closed due to inactivity. If you believe this ticket is still important, please reopen it and leave a comment to explain why. Thank you!

Generated at Thu Feb 08 08:06:09 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.