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

Disable chained replication before replSetAbortPrimaryCatchUp in direct_shard_connection_auth_rs_commands.js

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 8.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • Fully Compatible
    • CAR Team 2024-06-24
    • 200

      In the test, we are stopping replication on one secondary and then performing a write on the primary. We then wait for the write to be replicated to the second secondary. However, we are seeing that the secondary fails to replicate this change because its sync source is set as the other secondary whose replication has been paused. This can happen due to chained replication, as we saw in a similar test here. Disabling chaining will force the secondaries to replicate from the primary which should fix this issue.

            Assignee:
            allison.easton@mongodb.com Allison Easton
            Reporter:
            allison.easton@mongodb.com Allison Easton
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: