Details
-
Bug
-
Resolution: Cannot Reproduce
-
Major - P3
-
None
-
3.2.0
-
ALL
-
-
Platforms 18 (08/05/16), Platforms 2016-08-26, Platforms 2016-09-19, Platforms 2016-10-10
-
0
Description
fsm_all_sharded_replication_legacy_config_servers.js runs the FSM workloads against a sharded cluster with 2 mongos processes, 2 3-node replica-set shards, and 3 legacy config servers. None of the FSM workloads run (individually) with more than 20 threads. In this test, half of the clients communicate solely with one of the mongos processes, and the half of the client communicate solely with the other mongos process.
As the test is running, the mongos goes from having ~30 connections open to the primary of each of the replica-set shards to over 50. If this behavior is expected and desirable, then I think we should consider scaling the number of task executors in the pool down when test commands are enabled to avoid overwhelming our test hosts.