Connection lasts long time when one config server is off

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Duplicate
    • Priority: Major - P3
    • None
    • Affects Version/s: 3.0.8
    • Component/s: Networking, Sharding
    • None
    • Environment:
      Debian Wheezy
    • Linux
    • Hide

      sharded cluster with three config servers and authentication enabled
      run "poweroff" or "shutdown -h now" on one config server (not only stop service, completely shutdown the server)
      test some query and you will see

      Show
      sharded cluster with three config servers and authentication enabled run "poweroff" or "shutdown -h now" on one config server (not only stop service, completely shutdown the server) test some query and you will see
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Last week we had to make maintenance on server hardware where is one of the config servers. After server shutdown we had problems with timeouts on connections to mongos.
      From tests on staging environment:
      normal state

      -> time echo "db.system.version.find()" | mongo --username=someuser --password=somepassword admin
MongoDB shell version: 3.0.8
connecting to: admin
{ "_id" : "authSchema", "currentVersion" : 5 }
bye

real	0m0.149s
user	0m0.110s
sys	0m0.030s
}}

      degraded state (one server down)
-> time echo "db.system.version.find()" | mongo --username=someuser --password=somepassword admin
MongoDB shell version: 3.0.8
connecting to: admin
{ "_id" : "authSchema", "currentVersion" : 5 }
bye

real	0m38.845s
user	0m0.130s
sys	0m0.050s

            Assignee:
            Kelsey Schubert
            Reporter:
            Filip Havlí?ek
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: