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

shards_and_config_return_last_committed_optime.js shouldn't assume opTime in response equals opTime in metadata

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.0.11, 4.2.0-rc3, 4.3.1
    • Component/s: Sharding
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Requested:
      v4.2, v4.0
    • Sprint:
      Sharding 2019-07-15
    • Linked BF Score:
      12

      Description

      shards_and_config_return_last_committed_optime.js runs replSetGetStatus and asserts the last committed opTime timestamp in the response's body equals the last committed opTime metadata field in the response, which may not be true if the last committed opTime advances between executing the command and computing its metadata. The test should assert the last committed opTime in the metadata is >= the opTime in the response body instead.

        Attachments

          Activity

            People

            Assignee:
            jack.mulrow Jack Mulrow
            Reporter:
            jack.mulrow Jack Mulrow
            Participants:
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: