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

mongod reports "Too many open files" after the first config server was killed and finally crashed

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Cannot Reproduce
    • 2.2.1
    • None
    • Sharding
    • None
    • os: Debian 6.0 kernel: Linux 2.6.38-2-amd64
      cluster: a sharded cluster with 4 replica sets. Each rs contains a primary & a second & a arbiter (mongod v2.2.1)
    • Linux

    Description

      We tried to upgrade mongodb components from 2.2.1 to 2.2.2. (simply by kill & upgrade & start one by one component)
      Several minutes after we killed the first config server, one of mongod began to report "Too many open files", and it crashed several minutes later.

      The system's limit had already been set:
      Limit Soft Limit Hard Limit Units
      Max open files 65535 65535 files

      I guess in this situation, mongod opens too many files/sockets and forget to close them.
      Please look into the attachement, it contains full log from the time we kill the config server to the end.

      Attachments

        1. serverStatus.txt
          71 kB
        2. log.txt
          1023 kB

        Activity

          People

            thomas.rueckstiess@mongodb.com Thomas Rueckstiess
            strlee stronglee
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: