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

shard split jstest case should not depend on maxTimeMS to prove a tenant access blocker is installed

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 6.0.0-rc0
    • None
    • None
    • None
    • Fully Compatible
    • ALL
    • Server Serverless 2022-03-07, Server Serverless 2022-03-21, Server Serverless 2022-04-04
    • 19

    Description

      Currently, shard_split_tenant_access_blocking.js depends on the maxTimeMS to prove a tenant access blocker is installed by attempting a write. But, even if we get time out response, we still cannot say it's 100% caused by a tenant access blocker. 

      In this ticket, mtab.numBlockedWrites will be used the same purpose as the create_indexes_with_tenant_migration.js does.

      Attachments

        Activity

          People

            sophia.tan@mongodb.com Sophia Tan
            sophia.tan@mongodb.com Sophia Tan
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: