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

Tenant Migration Change Streams test should wait for replication

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 7.0.0-rc0
    • None
    • None
    • None
    • Serverless
    • Fully Compatible
    • 33

    Description

      There is a potential race condition in the shard split change stream test where calling `getTenantConnection` on secondary nodes could result in `NotWritablePrimary` (see investigation here) when the method attempts to create a user after not finding it.

      We should make sure that after calling `getTenantConnection` on the primary (which creates a new user for the tenant connection) that replication happened before calling getTenantConnection on the secondaries.

      We should also consider making the change in this shard merge test as well.

      Attachments

        Activity

          People

            christopher.caplinger@mongodb.com Christopher Caplinger
            mathis.bessa@mongodb.com Mathis Bessa
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: