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

Possibly deadlock reached while performing simultaneous queries and mapreduces

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • 1.5.6
    • 1.5.7
    • Querying
    • None
    • CentOS Linux 2.6.18-194.8.1.el5 SMP x86_64
    • Linux

    Description

      While performing simultaneous activities I was able to put a mongod 1.5.6 instance into a supposed deadlock. The server still accepts connections but will not perform further queries or mapreduces. I've included a currentOp output and a portion of stdout and stderr from mongod. Samples of the types of mapreduces and queries used can be gleaned from this output. The server was under heavy use with many processes/hosts concurrently querying and inserting and performing mapreduces.

      The mongod and the system is idle. I've tried interrupting the server with a response of "got kill or ctrl c or hup signal 2 (Interrupt), will terminate after current cmd ends". I've issued db.killOp requests which do not take effect.

      Attachments

        1. currentOp_output.txt
          8 kB
        2. mongdb_stdout_stderr.txt
          12 kB

        Activity

          People

            mathias@mongodb.com Mathias Stearn
            kkurzweil Ken Kurzweil
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: