1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
|
test_kind: fsm_workload_test
selector:
roots:
- jstests/concurrency/fsm_workloads/**/*.js
exclude_files:
##
# Blacklists from concurrency_sharded_replication
##
# 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
# 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 SERVER-20057, 'Concurrent, sharded mapReduces can fail when temporary
# namespaces collide across mongos processes'
- jstests/concurrency/fsm_workloads/map_reduce_drop.js
- jstests/concurrency/fsm_workloads/map_reduce_inline.js
- jstests/concurrency/fsm_workloads/map_reduce_interrupt.js
- jstests/concurrency/fsm_workloads/map_reduce_merge.js
- jstests/concurrency/fsm_workloads/map_reduce_merge_nonatomic.js
- jstests/concurrency/fsm_workloads/map_reduce_reduce.js
- jstests/concurrency/fsm_workloads/map_reduce_reduce_nonatomic.js
- jstests/concurrency/fsm_workloads/map_reduce_replace.js
- jstests/concurrency/fsm_workloads/map_reduce_replace_nonexistent.js
- jstests/concurrency/fsm_workloads/map_reduce_replace_remove.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_simultaneous_padding_bytes.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
# 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
# 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
# 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
# TODO SERVER-38190: Killing an operation committing a prepared txn can crash.
# TODO SERVER-38297: Killing session on a secondary applying a prepare oplog entry can crash.
# TODO SERVER-38299: Killing an operation preparing a transaction can crash.
- jstests/concurrency/fsm_workloads/multi_statement_transaction_kill_sessions_atomicity_isolation.js
# Expects reads to die with a particular error, but other errors are possible if the read is part
# of a transaction (e.g. ErrorCodes.LockTimeout).
- jstests/concurrency/fsm_workloads/drop_index_during_replan.js
##
# Blacklists from concurrency_replication_multi_stmt_txn
##
# Relies on having one thread observe writes from the other threads, which won't become visible
# once a transaction in the thread is started because it'll keep reading from the same snapshot.
- jstests/concurrency/fsm_workloads/create_index_background.js
- jstests/concurrency/fsm_workloads/create_index_background_partial_filter.js
- jstests/concurrency/fsm_workloads/create_index_background_wildcard.js
##
# Blacklists from concurrency_sharded_replication_multi_stmt_txn
##
# Use updates that do not contain the shard key, so they are rejected before any commands are
# sent to participant shards, but these workloads do not fail, so the auto retry transaction logic
# attempts to commit, which fails because no participants have been contacted.
- jstests/concurrency/fsm_workloads/update_rename.js
- jstests/concurrency/fsm_workloads/update_rename_noindex.js
# TODO SERVER-38387: Incorrectly sends a shardCollection command that will fail with
# InvalidOptions, which is normally ignored but this error is re-thrown with transactions enabled,
# failing the workload.
- jstests/concurrency/fsm_workloads/agg_out.js
# TODO SERVER-38569: Unblacklist this workload once the performance of sharded transactions has
# improved to avoid timeouts on slow variants.
- jstests/concurrency/fsm_workloads/remove_and_bulk_insert.js
exclude_with_any_tags:
- assumes_balancer_off
- requires_replication
# The touch command does not exist on mongos, which is enforced before session information is
# parsed, causing state functions in these workloads to fail before starting a transaction despite
# sending a command with startTransaction=true, leading to an infinite loop in the auto
# transaction retry override.
- requires_touch
# Sharing cursors between state functions will fail in this suite because it will attempt to use
# the same cursor in multiple transactions.
- state_functions_share_cursor
# These start a transaction in one state function and use it in other state functions. This suite
# would instead execute each state function as its own transaction.
- state_functions_share_transaction
# Are meant to test transactions with snapshot read concern.
- assumes_snapshot_transactions
executor:
archive:
hooks:
- CheckReplDBHash
- ValidateCollections
tests: true
config:
shell_options:
readMode: commands
global_vars:
TestData:
# Reads and writes outside of transactions will not have their read or write concerns
# changed.
defaultTransactionReadConcernLevel: "local"
defaultTransactionWriteConcernW: 1
runInsideTransaction: true
# Neither causal consistency nor majority write concern is required because tests in this
# suite only read from primaries, only one node is electable in each shard, and they use
# transactions with "local" level read concern, which should see all applied writes,
# including those that have not been majority replicated.
runningWithCausalConsistency: false
runningWithSessions: true
traceExceptions: false
usingReplicaSetShards: true
hooks:
- 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
# TODO SERVER-38302: Write noops to avoid hangs if the stable timestamp does not advance
# when the oldest prepared transaction commits or aborts.
periodicNoopIntervalSecs: 1
writePeriodicNoops: true
num_rs_nodes_per_shard: 3
num_shards: 2
num_mongos: 2
|
