-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Replication
-
ALL
-
0
-
None
-
None
-
None
-
None
-
None
-
None
-
None
The max_doc_size.js test, introduced in SERVER-12973, generally runs without issues in our CI system. However, in the burn-in test configuration, we have observed consistent memory resource issues running this test in the secondary_passthrough suite. This may be an issue of the VM type provisioned or a latent defect within the server code. The test will be disabled under this configuration to avoid patch build failures from changes unrelated to the memory footprint of the test and we will look into the memory issues separately.
- is related to
-
-
- Closed
-
-
SERVER-110061 Add names to update path error codes
-
- Needs Scheduling
-
-
SERVER-111065 provide unique namespaces for test cases in max_doc_size.js
-
- Closed
-
- related to
-
-
- Closed
-