Inconsistent handling of operation time in mongod error response

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Duplicate
    • Priority: Major - P3
    • None
    • Affects Version/s: 3.6.3, 3.7.1
    • Component/s: None
    • ALL
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      There is a logic in execCommandDatabase to differentiate between whether there is a valid operationTime:
      https://github.com/mongodb/mongo/blob/62ca1bcdd3dcc634a6fa91204b0f0941eb76399e/src/mongo/db/service_entry_point_mongod.cpp#L723

      However, the logic does not exist in runCommands:
      https://github.com/mongodb/mongo/blob/62ca1bcdd3dcc634a6fa91204b0f0941eb76399e/src/mongo/db/service_entry_point_mongod.cpp#L815

      This is inconsistent as runCommands calls execCommandDatabase and should therefore have the same logic.

            Assignee:
            Cheahuychou Mao
            Reporter:
            Randolph Tan
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: