Better logging when timeout is exceeded with getLastError

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Won't Fix
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Diagnostics
    • Query
    • Fully Compatible
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Currently when an operation exceeds the getLastError timeout value, we would see a message similar to the following:

      command admin.$cmd command: { getlasterror: 1, w: 2, wtimeout: 1000 } ntoreturn:1 reslen:112 1000ms

      Which is easily missed, and does not mention the actual problem - that the time out has been exceeded. A better log message indicating the that timeout had been exceeded would be more useful.

            Assignee:
            Backlog - Query Team (Inactive)
            Reporter:
            Andre de Frere
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: