-
Type: Bug
-
Resolution: Done
-
Priority: Critical - P2
-
None
-
Affects Version/s: None
-
Component/s: None
-
Labels:
-
Environment:
*Location*: https://docs.mongodb.com/ecosystem/platforms/windows-azure/
*User-Agent*: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.98 Safari/537.36
*Screen Resolution*: 1920 x 1200
-
2
Our recommendations for running MongoDB on Azure differ from this page to our Production Notes. They should be updated to match (preferably w/ an include to keep everything in-sync). See DOCS-6896 for reference.
Potential update:
Storage Considerations
Azure VMs can be configured with either ephemeral storage or persistent storage. Ephemeral storage is lost when instances are terminated, so it is generally not recommended unless you understand the data loss implications.
For most deployments Azure Persistent Storage will be the better choice. For production systems we recommend using:
- Premium Storage optimized VMs (e.g. DSv2, DS, GS, Fs)
- Premium Storage volumes
Storage configuration needs vary among deployments. Using separate volumes for data files, the journal, and the log may reduce I/O contention. Disks may be striped to increase volume size or throughput (for parallel operations). Choose a VM size large enough to accommodate the desired throughput.
- related to
-
DOCS-6896 Recommended changes to Azure related notes
- Closed