-
Type: Bug
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: 3.2.0-rc3
-
Component/s: Testing Infrastructure
-
None
-
Fully Compatible
-
ALL
-
-
QuInt C (11/23/15)
In order for an FSM workload's setup(), teardown(), and state functions to know the actual number of copies of itself that are running, the following initialization order is necessary.
- Apply the threadMultiplier.
- Call ThreadManager.prototype.init() to compute the actual number of copies of a workload that will run. This number may be less than the requested one to avoid resource issues on the test hosts.
- Define the read-only "threadCount" property on the $config.data object.
- Invoke the workload's setup() function.
Note that this issue doesn't affect any of the active fsm_all_xx.js tests that run in Evergreen because a single workload does not request to run with more than 100 threads.
[js_test:fsm_all] 2015-11-18T01:32:40.227-0500 ---- [js_test:fsm_all] 2015-11-18T01:32:40.227-0500 Workload(s) started: jstests/concurrency/fsm_workloads/threadcount.js [js_test:fsm_all] 2015-11-18T01:32:40.227-0500 ---- [js_test:fsm_all] 2015-11-18T01:32:40.227-0500 [js_test:fsm_all] 2015-11-18T01:32:40.227-0500 [js_test:fsm_all] 2015-11-18T01:32:40.227-0500 [js_test:fsm_all] 2015-11-18T01:32:40.227-0500 [js_test:fsm_all] 2015-11-18T01:32:40.227-0500 ---- [js_test:fsm_all] 2015-11-18T01:32:40.227-0500 setup() function sees threadCount=105 [js_test:fsm_all] 2015-11-18T01:32:40.228-0500 ---- [js_test:fsm_all] 2015-11-18T01:32:40.228-0500 [js_test:fsm_all] 2015-11-18T01:32:40.228-0500 [js_test:fsm_all] 2015-11-18T01:32:40.228-0500 Using 100 threads (requested 105)
- is depended on by
-
SERVER-21499 Enable fsm_all_simultaneous.js (FSM parallel mode)
- Closed
- is related to
-
SERVER-21310 Inject iterations and threadCount into data object in fsm workloads
- Closed