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

non_durable_writes_on_primary_can_reach_majority.js does not wait for durable timestamp on secondary to advance

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 5.0.4, 5.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • ALL
    • v5.0
    • Execution Team 2021-08-23
    • 25

      The fsync command on the secondary does not force the durable timestamp forward.

      The test passes most of the time because the journal flusher updates the durable optime in the TopologyCoordinator before the test calls replSetGetStatus.

            Assignee:
            benety.goh@mongodb.com Benety Goh
            Reporter:
            benety.goh@mongodb.com Benety Goh
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: