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

Always check client last operation time when computing operationTime to append to the response

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.3.4, 4.0.22, 4.2.12
    • Component/s: Sharding
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Requested:
      v4.2, v4.0
    • Sprint:
      Sharding 2020-03-09
    • Linked BF Score:
      5

      Description

      Currently, if a command has an uninitialized startOperationTime (because the client still has uninitialized opTime when the command starts running), computeOperationTime returns the replication coordinator's lastAppliedOpTime as the operationTime to append to the response for the command. This operationTime could sometimes be later than the opTime for the operation performed by the command. To prevent this, this block of code should be removed so that we always check and try to use the client last operation time when possible.

        Attachments

          Activity

            People

            Assignee:
            cheahuychou.mao Cheahuychou Mao
            Reporter:
            cheahuychou.mao Cheahuychou Mao
            Participants:
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: