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

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • 3.3.9
    • Affects Version/s: None
    • Component/s: Replication, Sharding
    • None
    • Fully Compatible
    • ALL
    • Sharding 16 (06/24/16)
    • 0

      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.

            Assignee:
            spencer@mongodb.com Spencer Brody (Inactive)
            Reporter:
            spencer@mongodb.com Spencer Brody (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: