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

Run periodic noop writer in nodes_in_primarys_datacenter_dont_sync_across_datacenters.js

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 7.0.0-rc0
    • None
    • None
    • None
    • Fully Compatible
    • ALL
    • Repl 2023-03-06
    • 5

    Description

      During the test, we expect a node to switch its sync source to be the primary. The test times out waiting for this to happen, but the node is never able to sync from the expected node since it isn't eligible. It looks like node 1 denylists the primary due to network issues, but by the time it re-evaluates the primary as a sync source, it has already caught up to it.

      The periodic noop writer should mean that the primary will keep advancing its optime, so it will be an eligible sync source after such network issues.

      Attachments

        Activity

          People

            samy.lanka@mongodb.com Samyukta Lanka
            samy.lanka@mongodb.com Samyukta Lanka
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: