-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Internal Code
-
None
-
Service Arch
-
Fully Compatible
-
v6.2, v6.0, v5.0, v4.4
-
Service Arch 2023-02-06
-
(copied to CRM)
Currently every invocation of _killOperations, an internal-only command, produces the following log for every operation key provided to the command:
template <typename Derived> class KillOperationsCmdBase : public TypedCommand<Derived> { public: ... void typedRun(OperationContext* opCtx) { auto opKiller = OperationKiller(opCtx->getClient()); auto opKeys = Base::request().getOperationKeys(); for (auto& opKey : opKeys) { LOGV2(4615602, "Attempting to kill operation", "operationKey"_attr = opKey); opKiller.killOperation(OperationKey(opKey)); } Derived::killCursors(opCtx, opKeys); } ...
This is potentially logged for every hedged operation, adding unnecessary noise to mongod logs. We should consider logging this at D1 or D2 to allow users suppress the log during normal operation.