Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-21907

mongos has more than 50 connections open to the primary of each replica-set shard

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • Icon: Major - P3 Major - P3
    • None
    • 3.2.0
    • Networking
    • ALL
    • Hide

      python buildscripts/resmoke.py --executor concurrency_sharded jstests/concurrency/fsm_all_sharded_replication_legacy_config_servers.js --storageEngine wiredTiger
      

      Some basic stats about the connections

      $ while true; do lsof -p <pid_of_mongos1,pid_of_mongos2> | grep "\->.*:2001[03].*ESTABLISHED" | wc -l; sleep 10; done
      73
      88
      94
      102
      122
      125
      125
      146
      156
      156
      156
      161
      161
      169
      186
      204
      205
      205
      205
      205
      205
      203
      197
      208
      211
      210
      210
      208
      206
      205
      205
      205
      205
      209
      209
      203
      200
      201
      211
      211
      211
      211
      211
      211
      211
      

      Show
      python buildscripts/resmoke.py --executor concurrency_sharded jstests/concurrency/fsm_all_sharded_replication_legacy_config_servers.js --storageEngine wiredTiger Some basic stats about the connections $ while true; do lsof -p <pid_of_mongos1,pid_of_mongos2> | grep "\->.*:2001[03].*ESTABLISHED" | wc -l; sleep 10; done 73 88 94 102 122 125 125 146 156 156 156 161 161 169 186 204 205 205 205 205 205 203 197 208 211 210 210 208 206 205 205 205 205 209 209 203 200 201 211 211 211 211 211 211 211
    • 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.

      Attachments

        Activity

          People

            jonathan.reams@mongodb.com Jonathan Reams
            max.hirschhorn@mongodb.com Max Hirschhorn
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: