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

Mongos stalls for even simple queries

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Done
    • Affects Version/s: 3.2.5
    • Fix Version/s: None
    • Component/s: Sharding
    • Labels:
      None
    • Operating System:
      ALL
    • Case:

      Description

      We have a 32 node cluster where each node is a 3 member replicaset having a hidden member.
      Cluster is running MongoDb 3.2.5 with WiredTiger on RHEL7.
      We see that some mongos processes get stuck and just do not return even for a very simple query while most other mongos processes are not affected.
      This happens to different nodes and is not limited to specific machines. It had happened yesterday on another machine and then after restarting the cluster, it happened on this machine.

      Queries like count() or show dbs or show collections that most probably access only the metadata - work fine on the mongos of the affected machine. However, running any simple query stalls the mongos.

      Attaching mongos logs for a mongos process that is not responding as well the config server primary node log.
      Note that the mongo processes were started with -v flag to increase logging verbosity

        Attachments

        1. bxb-ppe-oas006-mongos.stacks
          2.38 MB
        2. mongod.log-20161021-chi-ppe-oas009.gz
          62.56 MB
        3. mongodb_configdb-20161021-bxb-ppe-oas002.log.gz
          131.48 MB
        4. mongos_bxb-ppe-oas006.log
          2.29 MB
        5. mongos.log-20161021-bxb-ppe-oas010.gz
          103.13 MB
        6. mongos.log-20161021-bxb-ppe-oas010-after_restart.gz
          12 kB

          Issue Links

            Activity

              People

              • Votes:
                1 Vote for this issue
                Watchers:
                18 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: