test_kind: fsm_workload_test selector: roots: - jstests/concurrency/fsm_workloads/**/*.js exclude_files: # SERVER-13116 distinct isn't sharding aware - jstests/concurrency/fsm_workloads/distinct.js - jstests/concurrency/fsm_workloads/distinct_noindex.js - jstests/concurrency/fsm_workloads/distinct_projection.js # SERVER-17397 Drops of sharded namespaces may not fully succeed - jstests/concurrency/fsm_workloads/create_database.js - jstests/concurrency/fsm_workloads/drop_database.js - jstests/concurrency/fsm_workloads/map_reduce_drop.js # SERVER-14669 Multi-removes that use $where miscount removed documents - jstests/concurrency/fsm_workloads/remove_where.js # Disabled due to SERVER-33753, '.count() without a predicate can be wrong on sharded # collections'. This bug is problematic for these workloads because they assert on count() # values: - jstests/concurrency/fsm_workloads/agg_match.js # $lookup and $graphLookup are not supported on sharded collections. - jstests/concurrency/fsm_workloads/agg_graph_lookup.js - jstests/concurrency/fsm_workloads/view_catalog_cycle_lookup.js # Disabled due to MongoDB restrictions and/or workload restrictions # These workloads sometimes trigger 'Could not lock auth data update lock' # errors because the AuthorizationManager currently waits for only five # seconds to acquire the lock for authorization documents - jstests/concurrency/fsm_workloads/auth_create_role.js - jstests/concurrency/fsm_workloads/auth_create_user.js - jstests/concurrency/fsm_workloads/auth_drop_role.js - jstests/concurrency/fsm_workloads/auth_drop_user.js # uses >100MB of data, which can overwhelm test hosts - jstests/concurrency/fsm_workloads/agg_group_external.js - jstests/concurrency/fsm_workloads/agg_sort_external.js # compact can only be run against a standalone mongod - jstests/concurrency/fsm_workloads/compact.js - jstests/concurrency/fsm_workloads/compact_while_creating_indexes.js # convertToCapped can't be run on mongos processes - jstests/concurrency/fsm_workloads/convert_to_capped_collection.js - jstests/concurrency/fsm_workloads/convert_to_capped_collection_index.js # findAndModify requires a shard key - jstests/concurrency/fsm_workloads/findAndModify_mixed_queue_unindexed.js - jstests/concurrency/fsm_workloads/findAndModify_remove_queue_unindexed.js - jstests/concurrency/fsm_workloads/findAndModify_update_collscan.js - jstests/concurrency/fsm_workloads/findAndModify_update_queue.js - jstests/concurrency/fsm_workloads/findAndModify_update_queue_unindexed.js # remove cannot be {} for findAndModify - jstests/concurrency/fsm_workloads/findAndModify_remove_queue.js # can cause OOM kills on test hosts - jstests/concurrency/fsm_workloads/findAndModify_update_grow.js # cannot ensureIndex after dropDatabase without sharding first - jstests/concurrency/fsm_workloads/plan_cache_drop_database.js # reIndex is not supported in mongos. - jstests/concurrency/fsm_workloads/reindex.js - jstests/concurrency/fsm_workloads/reindex_background.js - jstests/concurrency/fsm_workloads/reindex_writeconflict.js # The WTWriteConflictException failpoint is not supported on mongos. - jstests/concurrency/fsm_workloads/collmod_writeconflict.js # our .remove(query, {justOne: true}) calls lack shard keys - jstests/concurrency/fsm_workloads/remove_single_document.js # The rename_* workloads are disabled since renameCollection doesn't work with sharded # collections - jstests/concurrency/fsm_workloads/rename_capped_collection_chain.js - jstests/concurrency/fsm_workloads/rename_capped_collection_dbname_chain.js - jstests/concurrency/fsm_workloads/rename_capped_collection_dbname_droptarget.js - jstests/concurrency/fsm_workloads/rename_capped_collection_droptarget.js - jstests/concurrency/fsm_workloads/rename_collection_chain.js - jstests/concurrency/fsm_workloads/rename_collection_dbname_chain.js - jstests/concurrency/fsm_workloads/rename_collection_dbname_droptarget.js - jstests/concurrency/fsm_workloads/rename_collection_droptarget.js # SERVER-20361 Improve the behaviour of multi-update/delete against a sharded collection - jstests/concurrency/fsm_workloads/update_where.js # cannot use upsert command with $where with sharded collections - jstests/concurrency/fsm_workloads/upsert_where.js # stagedebug can only be run against a standalone mongod - jstests/concurrency/fsm_workloads/yield_and_hashed.js - jstests/concurrency/fsm_workloads/yield_and_sorted.js # TODO Unblacklist (SERVER-35538). - jstests/concurrency/fsm_workloads/database_versioning.js # TODO Unblacklist (SERVER-38852). - jstests/concurrency/fsm_workloads/agg_out_interrupt_cleanup.js # serverStatus does not include transaction metrics on mongos. - jstests/concurrency/fsm_workloads/multi_statement_transaction_atomicity_isolation_metrics_test.js # Uses the same transaction id across different routers, which is not allowed because when either # router tries to commit, it may not know the full participant list. - jstests/concurrency/fsm_workloads/multi_statement_transaction_all_commands_same_session.js exclude_with_any_tags: - assumes_balancer_off - requires_replication executor: archive: hooks: - CheckReplDBHashInBackground - CheckReplDBHash - ValidateCollections tests: true config: shell_options: readMode: commands global_vars: TestData: usingReplicaSetShards: true hooks: - class: CheckReplDBHashInBackground - class: CheckReplDBHash - class: ValidateCollections - class: CleanupConcurrencyWorkloads fixture: class: ShardedClusterFixture mongos_options: set_parameters: enableTestCommands: 1 shard_options: mongod_options: oplogSize: 1024 mongod_options: set_parameters: enableTestCommands: 1 num_rs_nodes_per_shard: 3 num_shards: 2 num_mongos: 2