[DOCS-9415] Update mongodb-ecosystem/platforms/windows-azure.txt to be in-sync w/ Production Notes Created: 30/Nov/16 Updated: 26/Jan/17 Resolved: 26/Jan/17 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Critical - P2 |
| Reporter: | Nicholas Tang | Assignee: | Andrew Aldridge |
| Resolution: | Done | Votes: | 0 |
| Labels: | collector-298ba4e7 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Location: https://docs.mongodb.com/ecosystem/platforms/windows-azure/ |
||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Days since reply: | 7 years, 5 weeks, 1 day ago | ||||||||
| Story Points: | 2 | ||||||||
| Description |
|
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 Potential update: Storage ConsiderationsAzure 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:
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. |
| Comments |
| Comment by Githook User [ 10/Jan/17 ] |
|
Author: {u'username': u'i80and', u'name': u'Andrew Aldridge', u'email': u'i80and@foxquill.com'}Message: |
| Comment by Githook User [ 07/Jan/17 ] |
|
Author: {u'username': u'i80and', u'name': u'Andrew Aldridge', u'email': u'i80and@foxquill.com'}Message: |