-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Query Execution
-
Fully Compatible
-
ALL
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Follow-up to SERVER-134664, which added default-verbosity LOGV2 lines when a query is rejected by maxEstimatedScanBytes (unbounded COLLSCAN exceeding the configured threshold).
The new log lines are emitted on every rejection without rate limiting, so a burst of rejected queries against one or more large collections can spam the mongod log.
Rate-limit these rejection log lines using logv2::SeveritySuppressor (or logv2::KeyedSeveritySuppressor keyed by namespace, so each offending namespace is logged once per time window).
- is related to
-
SERVER-134664 maxEstimatedScanBytes query rejection is not logged at default verbosity
-
- Closed
-