Tenant Migration Change Streams test should wait for replication

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 7.0.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Serverless
    • Fully Compatible
    • 33
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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.

              Assignee:
              Christopher Caplinger
              Reporter:
              Mathis Bessa (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: