TaskRunner must ensure Client is initialized for thread before running tasks

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 3.4.18, 3.6.9, 4.0.4, 4.1.4
    • Affects Version/s: 3.4.16, 3.6.7, 4.0.2, 4.1.2
    • Component/s: Replication
    • None
    • Fully Compatible
    • ALL
    • v4.0, v3.6, v3.4
    • Repl 2018-09-24
    • 46
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      If TaskRunner::_runTasks() never runs the body of this loop (for example, due to a shutdown request), then it will never initialize the Client for the thread. Then, when it cancels tasks, it there will be no Client set on the thread. This means it will be illegal for the task to call Client::cc(). TaskRunner::_runTasks() should ensure the Client is initialized before running runSingleTask().

            Assignee:
            Tess Avitabile (Inactive)
            Reporter:
            Tess Avitabile (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: