[DOCS-10914] Update 'connections limit' table to account for M2, M5 Created: 18/Oct/17 Updated: 29/Oct/23 Resolved: 25/Jan/18 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | Atlas |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Jeffrey Numark | Assignee: | Irene Smith |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | docs-triage | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Participants: | |||||
| Days since reply: | 6 years, 2 weeks, 6 days ago | ||||
| Epic Link: | DOCSP-1743 | ||||
| Story Points: | 0.1 | ||||
| Description |
|
https://docs.atlas.mongodb.com/connect-to-cluster/ This table should reflect the maximum number of connections to M2 and M5 clusters as well. |
| Comments |
| Comment by Irene Smith [ 25/Jan/18 ] |
|
New rows added to connection limits table for M2 and M5 |
| Comment by Andrew Walsh [ 18/Dec/17 ] |
|
ravind.kumar M2 and M5 instance sizes have the same connection limit of 100 as does the M0:
/r |
| Comment by Ravind Kumar (Inactive) [ 25/Oct/17 ] |
|
cory.mintz ping! |