-
Type:
Bug
-
Resolution: Gone away
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Workload Resilience
-
ALL
-
200
-
None
-
None
-
None
-
None
-
None
-
None
-
None
This variant is meant to test graceful degradation under materialization pressure. the point is presumably to watch mongotune/the server adapt to a slow page service — which requires the workload to actually run. The long-term fix is server-side: write admission / flow control that throttles ingest when the unmaterialized log grows — that would make any workload degrade gracefully instead of erroring.