[SERVER-35208] Use large instance type for certain concurrency suites Created: 24/May/18 Updated: 29/Oct/23 Resolved: 01/Jun/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | 4.0.0-rc0 |
| Fix Version/s: | 4.0.0-rc2, 4.1.1 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Robert Guo (Inactive) | Assignee: | Robert Guo (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||
| Backport Requested: |
v3.6
|
||||||||||||||||||||
| Sprint: | TIG 2018-06-04, TIG 2018-06-18 | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Description |
|
We should use "large" instance types for the concurrency_replication_causal_consistency suites. They start 5 nodes that each have a 1GB oplog and 1GB WT cache, this overwhelms our "small" instances which have 7.5GB memory. We workaround the problem at the moment by running CleanEveryN to remove the data files and restart the cluster, so the oplog doesn't get too big. Similarly, concurrency sharded and replication suites on the linux repeated builder should also run on the large instance type. |
| Comments |
| Comment by Githook User [ 04/Jun/18 ] |
|
Author: {'username': 'guoyr', 'name': 'Robert Guo', 'email': 'robert.guo@10gen.com'}Message: (cherry picked from commit d0b8d07d0a30c570a76ab902560d896810b5825e) |
| Comment by Githook User [ 01/Jun/18 ] |
|
Author: {'username': 'guoyr', 'name': 'Robert Guo', 'email': 'robert.guo@10gen.com'}Message: |