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

Disallow chaining in change_stream_update_lookup_read_concern.js

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.1.11, 4.0.12
    • Component/s: None
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Requested:
      v4.0
    • Linked BF Score:
      25

      Description

      The change_stream_update_lookup_read_concern.js test creates a repl set and assumes that the two secondaries both sync from the primary. In a few cases, the TopologyCoordinator instead syncs one of the secondaries from the other. The test is supposed to temporarily turn off replication on one secondary, but the unfortunate chaining situation means that replication effectively gets disabled on both secondaries, deadlocking the test.

      Disabling chaining should prevent this failure from occurring again.

        Attachments

          Activity

            People

            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: