makeExhaustMessage should no longer call OpMsg::parse

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 4.2.1, 4.3.1
    • Affects Version/s: None
    • Component/s: Replication
    • None
    • Fully Compatible
    • v4.2
    • Repl 2019-06-17, Repl 2019-07-01
    • 0
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      makeExhaustMessage()should no longer call OpMsg::parse on the previous response message. Instead, it should get the cursor info directly from DBResponse object. Also, it should return empty message if either DBResponse::exhaustNS is empty or DBResponse::exhaustCursorId is equal to 0.

            Assignee:
            Vishnu Kaushik
            Reporter:
            Jason Chan
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: