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

ReplSetTest.awaitLastOpCommitted can fail to wait for the last op to be committed

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.3.9
    • Component/s: Replication, Sharding
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Sprint:
      Sharding 16 (06/24/16)
    • Linked BF Score:
      0

      Description

      ReplSetTest.awaitLastOpCommitted depends on comparing Timestamps, but Timestamp comparison in the shell is broken (per SERVER-21861). This means that if the committed optime of two servers differs only in the increment portion of the Timestamp, we might return before all servers are actually caught up.

        Attachments

          Issue Links

          is related to

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-21861 Better Timestamp object comparison in mongo shell

          • Major - P3 - Major loss of function.
          • Closed

            Activity

              People

              Assignee:
              spencer Spencer Brody (Inactive)
              Reporter:
              spencer Spencer Brody (Inactive)
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: