-
Type:
Sub-task
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: 8.2.5, 8.0.19
-
Component/s: None
-
Workload Resilience
-
Workload Scheduling 2025-09-15, Workload Resilience 2025-09-29, Workload Resilience 2025-10-13, Workload Resilience 2025-10-27, Workload Resilience 2025-11-10, Workload Resilience 2025-11-24, Workload Resilience 2025-12-08, Workload Resilience 2025-12-22, Workload Resilience 2026-01-05, Workload Resilience 2026-01-19, Workload Resilience 2026-02-02, Workload Resilience 2026-02-16, Workload Resilience 2026-03-02, Workload Resilience 2026-03-16, Workload Resilience 2026-03-30, Workload Resilience 2026-04-13, Workload Resilience 2026-05-11, Workload Resilience 2026-04-13, Workload Resilience 2026-05-25, Workload Resilience 2026-06-08, Workload Resilience 2026-06-22, Workload Resilience 2026-07-06, Workload Resilience 2026-07-20, Workload Resilience 2026-08-03, Workload Resilience 2026-08-17, Workload Resilience 2026-08-31, Workload Resilience 2026-09-14
-
None
-
None
-
None
-
None
-
None
-
None
-
None
The test `VerifyCacheSize` from the ` tcmalloc_set_parameters_test` unittest fails in a containerized environment (inside Docker) with:
{"t":{"$date":"2025-10-07T14:12:40.933Z"},"s":"I", "c":"TEST", "id":23065, "ctx":"main","msg":"Totals","attr":{"totals":{"name":"TOTALS","tests":13,"fails":1,"asserts":0,"time":{"durationMillis":9},"failures":[{"test":"VerifyCacheSize","type":"TestAssertionFailureException","error":"Expected std::abs((tcmallocCapacity) - (targetSize)) <= 1024 * 10 (1073741824 <= 10240) @src/mongo/util/tcmalloc_set_parameter_test.cpp:380"}]}},"truncated":{"totals":{"truncated":{"failures":{"truncated":{"0":{"truncated":{"extra":{"type":"string","size":16451}},"omitted":1}}}}}},"size":{"totals":16790}}
The workaround is to start the container with a hard memory limit, aka `docker run --memory=16g`
- is related to
-
SERVER-109273 Account for "max" in CGroups v2 memory limit parser (tcmalloc version)
-
- Open
-