Reduce severity or remove log message for PlanExecutor::DEAD error during find

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 4.0.7, 4.1.7, 3.6.20
    • Affects Version/s: None
    • Component/s: Querying
    • None
    • Fully Compatible
    • v4.0, v3.6
    • 0
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      this message is logged with 'error', but it's not clear it should rise to that level. For instance - it can happen if a PlanExecutor is killed because a collection is dropped while it was executing. In cases like this, nothing happened to corrupt server state or anything like that, so it's probably not worthy of a higher severity than log, and possibly even should be at a higher log level than 0.

            Assignee:
            Bernard Gorman
            Reporter:
            Charlie Swanson
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: