Uploaded image for project: 'Documentation'
  1. Documentation
  2. DOCS-9415

Update mongodb-ecosystem/platforms/windows-azure.txt to be in-sync w/ Production Notes

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Critical - P2 Critical - P2
    • None
    • Affects Version/s: None
    • Component/s: None
    • Environment:
    • 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.

            Assignee:
            andrew.aldridge@mongodb.com Andrew Aldridge
            Reporter:
            nicholas.tang@mongodb.com Nicholas Tang
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved:
              7 years, 16 weeks, 2 days ago