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

Split up long-running Evergreen tasks into shorter execution units

    XMLWordPrintable

    Details

      Description

      The following test suites when run on the Enterprise RHEL 6.2, Linux DEBUG, and Enterprise Windows 2008R2 cause the makespan to exceed 1 hour. We should use the script from SERVER-34296 to split them into test suites that take no longer than 20 minutes in order to reap concurrency benefits by running on separate EC2 instances. The Evergreen tasks added to the etc/evergreen.yml project configuration should be done under a display task of the original name in order to limit the Evergreen UI differences Server team engineers would otherwise encounter.

      • replica_sets_auth.yml (~1h on Enterprise Windows 2008R2)
      • replica_sets_ese.yml (~1h on Enterprise Windows 2008R2)
      • sharding.yml (~50m on Enterprise RHEL 6.2, ~1h20m on Linux DEBUG)
      • sharding_auth.yml (~50m on Enterprise RHEL 6.2, ~1h10m on Linux DEBUG, ~1h40m on Enterprise Windows 2008R2)
      • sharding_ese.yml (~50m on Enterprise RHEL 6.2, ~1h50m on Enterprise Windows 2008R2)
      • sharding_last_stable_mongos_and_mixed_shards.yml (~50m on Enterprise RHEL 6.2)
      • sharding_op_query.yml (~50m on Enterprise RHEL 6.2)
      • sharding_auth_audit.yml (~45m on Enterprise RHEL 6.2, ~1h45m on Enterprise Windows 2008R2, but only runs after sharding_auth Evergreen task completes)

      https://evergreen.mongodb.com/build/mongodb_mongo_master_enterprise_rhel_62_64_bit_c3badcbbcf069f428a765ba5937106d1da814076_18_04_05_00_46_39
      https://evergreen.mongodb.com/build/mongodb_mongo_master_linux_64_debug_f00b908d2bf6cca4c2527eaa88b0ae79d745fd0b_18_04_05_02_02_23
      https://evergreen.mongodb.com/build/mongodb_mongo_master_enterprise_windows_64_2k8_2e31167d0e2cf179a228afeec71853cfb0f0683f_18_04_05_00_06_12

      Note: The write_concern_majority_passthrough Evergreen task takes ~50m on Linux DEBUG; however, that seems more likely to be due to the removeb.js, mr1.js, remove9.js, geo_s2sparse.js, and queryoptimizer3.js tests taking longer than 15 minutes. We should look to modify these tests in a similar fashion to the changes in SERVER-33645 under a separate ticket.

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                6 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: