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

Add a build variant for large transactions

    XMLWordPrintableJSON

Details

    • Fully Compatible
    • Repl 2019-05-20, Repl 2019-06-03

    Description

      We reply on passthrough test suites for transactions test coverage. There are only 3 targeted test suites for large transactions:

      • core_txns_multi_oplog_entries
      • replica_sets_multi_oplog_txns
      • replica_sets_multi_oplog_txns_jscore_passthrough

      We need a build variant to leverage the passthrough test coverage of transactions. The tests should set the maxNumberOfTransactionOperationsInSingleOplogEntry to 1.

      The new build variant should include the following test suites since they runs at least one test file that includes "startTransaction".

      • auth
      • auth_audit
      • causally_consistent_jscore_txns_passthrough
      • change_streams
      • change_streams_whole_cluster_passthrough
      • change_streams_whole_db_passthrough
      • concurrency_replication
      • concurrency_replication_ubsan
      • concurrency_sharded_replication
      • concurrency_sharded_replication_with_balancer
      • concurrency_sharded_with_stepdowns
      • concurrency_sharded_with_stepdowns_and_balancer
      • core_txns
      • core_txns_multi_oplog_entries
      • logical_session_cache_replication_100ms_refresh_jscore_passthrough
      • logical_session_cache_replication_10sec_refresh_jscore_passthrough
      • logical_session_cache_replication_1sec_refresh_jscore_passthrough
      • logical_session_cache_replication_default_refresh_jscore_passthrough
      • multiversion
      • multiversion_auth
      • no_passthrough
      • replica_sets
      • replica_sets_auth
      • replica_sets_ese
      • replica_sets_ese_gcm
      • replica_sets_initsync_jscore_passthrough
      • replica_sets_initsync_static_jscore_passthrough
      • replica_sets_jscore_passthrough
      • replica_sets_kill_secondaries_jscore_passthrough
      • replica_sets_multi_oplog_txns
      • replica_sets_multi_oplog_txns_jscore_passthrough
      • replica_sets_multi_stmt_txn_jscore_passthrough
      • replica_sets_multi_stmt_txn_kill_primary_jscore_passthrough
      • replica_sets_multi_stmt_txn_stepdown_jscore_passthrough
      • replica_sets_multi_stmt_txn_terminate_primary_jscore_passthrough
      • sharded_causally_consistent_jscore_txns_passthrough
      • sharded_collections_causally_consistent_jscore_txns_passthrough
      • sharded_jscore_txns
      • sharded_jscore_txns_sharded_collections
      • sharded_multi_stmt_txn_jscore_passthrough
      • sharding
      • sharding_auth
      • sharding_auth_audit
      • sharding_continuous_config_stepdown
      • sharding_ese
      • sharding_ese_gcm
      • sharding_misc

      The build variant should also include the following ones, since resmoke -f doesn't work well with JS overrides. These test suites include "txn" in their names.

      • concurrency_replication_multi_stmt_txn
      • concurrency_replication_multi_stmt_txn_ubsan
      • concurrency_sharded_local_read_write_multi_stmt_txn
      • concurrency_sharded_local_read_write_multi_stmt_txn_with_balancer
      • concurrency_sharded_multi_stmt_txn
      • concurrency_sharded_multi_stmt_txn_with_balancer
      • concurrency_sharded_multi_stmt_txn_with_stepdowns
      • multi_shard_local_read_write_multi_stmt_txn_jscore_passthrough
      • multi_shard_multi_stmt_txn_jscore_passthrough
      • multi_shard_multi_stmt_txn_kill_primary_jscore_passthrough
      • multi_shard_multi_stmt_txn_stepdown_primary_jscore_passthrough
      • multi_stmt_txn_jscore_passthrough_with_migration

       

      Attachments

        Activity

          People

            jason.chan@mongodb.com Jason Chan
            siyuan.zhou@mongodb.com Siyuan Zhou
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: