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

Use a new database for the bucket_unpacking_with_sort_extended_range.js test

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 8.1.0-rc0, 8.0.5
    • Affects Version/s: 7.3.0, 8.0.0
    • Component/s: None
    • None
    • Catalog and Routing
    • Fully Compatible
    • ALL
    • v8.0
    • CAR Team 2024-10-14
    • 0

      bucket_unpacking_with_sort_extended_range.js is currently using the default database name "test" to run the validations.

      Since this test is run in a passthrough suite, other tests may have introduced data or already created the database with unexpected metadata. Because of that and to ensure a clean setup, the test drops the database at the startup.

      In slower variants, dropping the "test" database may take longer than 5 minutes. If the CheckMetadataConsistency hook is executed at the beginning of the test, it may timeout because it will not acquire the DDL lock within 5 minutes due to the ongoing dropDatabase operation.

      I suggest using a new database with the name of the test instead of reusing the "test" database from the passthrough.

            Assignee:
            pol.pinol@mongodb.com Pol Pinol
            Reporter:
            pol.pinol@mongodb.com Pol Pinol
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: