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

MongoDB stuck after db.getServerStatus().globalLock.currentQueue.writers exceeds 128 (windows)

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Critical - P2
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.0.0-rc0
    • Component/s: Concurrency
    • Labels:
      None
    • Environment:
      Reproduced on Windows 7 64-bit on 5 seperate machines.
    • Operating System:
      Windows

      Description

      Reproduce using java program : http://pastie.org/1428863

      Change CONNECTION_COUNT to 128 and the problem disappears, 129 or higher and the problem occurs 100% of the time on fast machines. Slower machines tend to not reach the 128 current lock point.

      db.serverStatus().globalLock.currentQueue.writers will show 128 and not recover, regardless of load or wait time. Verify by doing db.test.getIndexes(), it never returns after this.

      mongostats output after test to confirm load is in fact gone : http://pastie.org/1428842

      Other hosts can successfully connect to the same mongo instance.

        Attachments

          Activity

            People

            • Votes:
              3 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: