The case of running the server with --repair causing spurious warnings of ClientCursor::yield appearing in the logs was resolved in SERVER-4726. The same warnings appear when using db.runCommand(
) from the shell (or it's helper db.repairDatabase()).
While the warnings are informational only, and the repairDatabase appears to be working correctly, they do cause excessive log size. Even rotated logs of this message could be filled with mostly useless information for a large enough database.
- is duplicated by
-
SERVER-12217 repairDatabase() floods the log with recursive lock warning messages
- Closed
- related to
-
SERVER-4726 Spurious warning: ClientCursor::yield can't unlock b/c of recursive lock during --repair
- Closed
-
SERVER-13144 Size value is ignored when creating non-capped collections
- Closed
-
SERVER-13146 An _id index is built on the local.startup_log collection by default
- Closed
-
SERVER-4846 Rate limit ClientCursor::yield recursive lock warning
- Closed
-
SERVER-56424 improve index build invariant message for system error ENOSPC "28: No space left on device"
- Closed