The originatingCommand is missing in getMore 'Slow query' log upon error

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.2.0-rc0
    • Affects Version/s: 7.0.21, 8.0.10, 8.1.1
    • Component/s: None
    • None
    • Catalog and Routing
    • Fully Compatible
    • ALL
    • CAR Team 2025-06-09
    • None
    • 3
    • TBD
    • 🟩 Routing and Topology
    • None
    • None
    • None
    • None
    • None
    • None

      If a getMore operation fails before setting the originating command in the CurOp, the originating command will not be printed in the Slow query log, making debugging the error difficult.

      It's likely to fail a getMore operation during the locks acquisition, which is done before setting the originating command.

            Assignee:
            Silvia Surroca
            Reporter:
            Silvia Surroca
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: