-
Type:
Bug
-
Resolution: Duplicate
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Catalog and Routing
-
ALL
-
CAR Team 2025-06-09
-
1
-
None
-
3
-
TBD
-
🟦 Shard Catalog
-
None
-
None
-
None
-
None
-
None
-
None
In SERVER-100163, we introduced a log to track when a range deletion killed a query on a secondary.
This log must include the `originatingCommand` field, especially when the command is `getMore`.
The goal of this ticket is to understand why the `originatingCommand` is not set here, which probably means that the setOriginatingCommand() is called after the acquisition of the collection.
- is caused by
-
SERVER-100163 Ensure there is a log message when a query gets killed due to a Range Deletion
-
- Closed
-
- is duplicated by
-
-
- Closed
-
- is related to
-
-
- Closed
-