Rename collection errors due to "target namespace exists" after namespace was dropped in jstest

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • Catalog and Routing
    • Fully Compatible
    • ALL
    • CAR Team 2025-03-03
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      As part of SERVER-84330, transactions_block_ddl.js was unblocked in sharded environments. In sharded environments the rename command here fails (and below in the replica set endpoint case across dbs) because the rename command issued fails NamespaceExists even though the collection is dropped before running the test and the previous call to 'testTimeout' shouldn't create it. Preliminary investigation is in the comments.

      To reproduce, unblock the rename on mongos and run the test with the suite sharded_jscore_txns. 

              Assignee:
              Paolo Polato
              Reporter:
              Kristina Znam
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: