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

FSMWorkloadTestCase erroneously sets TestData.sameDB=true and TestData.sameCollection=true

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 4.0.1, 4.1.1
    • Testing Infrastructure
    • None
    • Fully Compatible
    • ALL
    • v4.0, v3.6
    • TIG 2018-07-02, TIG 2018-07-16

    Description

      The logic in the FSMWorkloadTestCase class is faulty because it sets TestData.sameDB=true when same_db=false and TestData.sameCollection=true when same_collection=false. However, these options currently have no effect because resmoke_runner.js doesn't define clusterOptions.sameDB and clusterOptions.sameCollection based on their associated TestData equivalents.

      # We use a global incrementing counter as a prefix for the database name to avoid any
      # collection lifecycle related issues in sharded clusters. This more closely matches how
      # uniqueDBName() and uniqueCollName() would have returned distinct values when called once
      # for each FSM workload in the entire schedule by runner.js.
      test_prefix = self.db_name_prefix if self.db_name_prefix else "test"
      test_data["dbNamePrefix"] = "{}{:d}_".format(test_prefix, count)
      if not self.same_db:
          test_data["sameDB"] = True
      if not self.same_collection:
          test_data["sameCollection"] = True
      

      Attachments

        Issue Links

          Activity

            People

              robert.guo@mongodb.com Robert Guo
              max.hirschhorn@mongodb.com Max Hirschhorn
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: