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

Inconsistent handling of operation time in mongod error response

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Duplicate
    • Affects Version/s: 3.6.3, 3.7.1
    • Fix Version/s: None
    • Component/s: None
    • Labels:
    • Operating System:
      ALL

      Description

      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.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              cheahuychou.mao Cheahuychou Mao
              Reporter:
              renctan Randolph Tan
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: