Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-45775

responseTo does not match requestId for exhaust awaitable ismaster

    XMLWordPrintableJSON

Details

    • Icon: New Feature New Feature
    • Resolution: Won't Fix
    • Icon: Major - P3 Major - P3
    • None
    • None
    • Replication
    • None
    • Fully Compatible
    • Repl 2020-02-10

    Description

      My expectation was that if I sent an imaster request with the exhaustAllowed bit set and a requestId of 42, that subsequent responses would indicate a responseTo: 42 with the moreToCome bit set. Instead, I'm seeing that moreToCome is set, but the responseTo field changes on each response. My guess is that the exhaust support for awaitable ismaster is using an internal mechanism to simulate getMore requests.

      Is it possible to maintain the original requestId for the lifetime of the request in these cases? Otherwise, a driver will be required to develop custom logic only for this command.

      Attachments

        Activity

          People

            tess.avitabile@mongodb.com Tess Avitabile (Inactive)
            matt.broadstone@mongodb.com Matt Broadstone
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: