A streaming isMaster that fails via failCommand still includes the OP_MSG moreToCome flag

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Cannot Reproduce
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • ALL
    • v4.4
    • Service arch 2020-10-19
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      When the failCommand failpoint is configured to fail a streaming isMaster, the server's ok:0 response mistakenly includes the OP_MSG moreToCome flag. Can we also confirm that the server will never set moreToCome on a ok:0 response in practice?

      Note that wether the server includes moreToCome or not on a ok:0 response shouldn't matter because the client will close the connection after reading the ok:0 response (See SDAM's network or command error during server check).

      CC: jeff.yemin

            Assignee:
            Amirsaman Memaripour
            Reporter:
            Shane Harvey
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: