[DOCS-4057] Improve the Blockstore DB setup recommendations Created: 17/Sep/14 Updated: 16/Mar/15 Resolved: 17/Oct/14 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | Cloud Manager |
| Affects Version/s: | None |
| Fix Version/s: | v1.3.12 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Anil Kumar | Assignee: | Bob Grabar |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 9 years, 17 weeks, 5 days ago |
| Description |
|
Our Blockstore DB recommended setup provides a naive approach by specifying just 2 data nodes. This organically implies that we can run MMS Backup in 2+1 topology for the Blockstore DB. Since MMS uses w=2 write concern this also implies that anyone using this setup would be susceptible to loss of write availability on Backup if they loose one of the data notes. We should enhance our documentation to make this clear in the recommended setup as well as any other place discussing high availability. |
| Comments |
| Comment by Githook User [ 17/Oct/14 ] |
|
Author: {u'username': u'bgrabar', u'name': u'Bob Grabar', u'email': u'bob.grabar@10gen.com'}Message: |