[SERVER-41079] Add a build variant for large transactions Created: 09/May/19  Updated: 29/Oct/23  Resolved: 16/May/19

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 4.1.12

Type: Task Priority: Major - P3
Reporter: Siyuan Zhou Assignee: Jason Chan
Resolution: Fixed Votes: 0
Labels: bigtxns_testing
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Repl 2019-05-20, Repl 2019-06-03
Participants:

 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

 



 Comments   
Comment by Githook User [ 16/May/19 ]

Author:

{'name': 'Jason Chan', 'email': 'jason.chan@10gen.com', 'username': 'jasonjhchan'}

Message: SERVER-41079 Add new build variant for the multiple oplog entries transaction format
Branch: master
https://github.com/mongodb/mongo/commit/6f8e35deddb2bd0039e06e5fab540786a91ac9bc

Comment by Githook User [ 16/May/19 ]

Author:

{'name': 'Jason Chan', 'email': 'jason.chan@10gen.com', 'username': 'jasonjhchan'}

Message: Revert "SERVER-41079 Add new build variant for the multiple oplog entries transaction format"

This reverts commit 6df77aa1579d11894a80ddd2edb3053db5abd0aa.
Branch: master
https://github.com/mongodb/mongo/commit/36c2f8b3416123000d3c56e6cf1b2968d356c4bc

Comment by Githook User [ 16/May/19 ]

Author:

{'email': 'jason.chan@10gen.com', 'name': 'Jason Chan', 'username': 'jasonjhchan'}

Message: SERVER-41079 Add new build variant for the multiple oplog entries transaction format
Branch: master
https://github.com/mongodb/mongo/commit/6df77aa1579d11894a80ddd2edb3053db5abd0aa

Comment by Siyuan Zhou [ 13/May/19 ]

As jason.chan suggested offline, we will set maxNumberOfTransactionOperationsInSingleOplogEntry to 2 in this new build variant, so that we'll have a better coverage on unwrapping logic.

Generated at Thu Feb 08 04:56:46 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.