[SERVER-61975] Fix memory issues Created: 09/Dec/21 Updated: 28/Feb/22 Resolved: 28/Feb/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 6.0 Desired |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Tausif Rahman (Inactive) | Assignee: | Tausif Rahman (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Sprint: | STM 2022-01-10, STM 2022-01-24 | ||||||||
| Participants: | |||||||||
| Story Points: | 2 | ||||||||
| Description |
|
As is, resmoke cannot run concurrency sharded test suites against an existing MongoDB cluster (non fixture). This is needed so that we can run tests against a sharded cluster in antithesis. |
| Comments |
| Comment by Brooke Miller [ 30/Dec/21 ] |
|
Moving this back to Open since we're waiting to hear back from Antithesis since they need to test our proposed suggestions |
| Comment by Tausif Rahman (Inactive) [ 28/Dec/21 ] |
|
Moving this back to in progress. As of now, we can run a concurrency sharded test suite in Antithesis, but there are some issues on the Antithesis side with Memory issues when Antithesis runs for a long period of time. We are working with Antithesis to resolve this. Once this issue is resolved, we will mark this as complete. |