replication_consistency_markers_impl_bm should skip direct shard operation checks

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.1.0-rc0, 7.3.2, 8.0.0-rc3
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • Fully Compatible
    • ALL
    • v8.0, v7.3, v7.0
    • CAR Team 2024-04-29
    • 143
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      The replication_consistency_markers_imply_bm is never initializing the ShardingState but is using AutoGetCollection during the test. AutoGetCollection is one of the places where the direct shard operation checks are performed, which uses the sharding state to determine whether the cluster is sharded.

      The test can skip the direct connection checks using the failpoint `skipDirectConnectionChecks`.

              Assignee:
              Allison Easton
              Reporter:
              Allison Easton
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: