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

Mongos crashes by few seconds of DB locking (or network delay).

    • Type: Icon: Bug Bug
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 2.0.9, 2.2.4, 2.4.3
    • Component/s: Sharding, Stability
    • None
    • Environment:
      CentOS release 6.4 (Final) x86_64
    • ALL

      I run Mongos on each WEB servers.
      And I set timeout to 1 seconds for each query due to peculiar and general form of the WEB.

      I'm suffering from sudden mongos death.
      It seems like caused by delay of the query from mongos to Mongod.

      Mongos will create a thread per mongos-mongod connections.
      When some queries delayed, Mongos will create new connection and thread to handle the request from APP.
      But these new connection will be delayed while DB locking.

      So Mongos continue to create threads , and die in the end.

      I confirmed that the number of the Mongos's threads exceed more than 300 when minor network delay (less than 10 seconds).

      I think that the "thread model of Mongos" is unlikely to work well in severe situation.

            Assignee:
            Unassigned Unassigned
            Reporter:
            crumbjp Hiroaki
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: