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

2.2.0-rc1 stops responding to other requests with high-fault reads?

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • 2.2.0-rc2, 2.3.0
    • Affects Version/s: 2.2.0-rc1
    • Component/s: Performance
    • Labels:
      None
    • Environment:
    • Linux

      I upgraded one server in a 6-server 2.0.1 replicaSet to test MongoDB 2.2.0-rc1. I wanted to test read and locking performance so I switched to a db with a very large collection that easily exceeds RAM. I then ran a query that I knew would match no records: db.collection.find(

      {x: 1}

      ). This caused the mongostat I was running in another window to stop responding, I could connect with another shell but "show dbs" would not return until the above query completed. Also, hitting Ctrl-C on the find() query caused "Fri Aug 17 19:07:19 Assertion: 13111:field not found, expected type 2" in the shell. I was unable to manually kill the find() operation.

      I also tried this a second time so I could be sure that as much of the database that could be hot in memory was available.

            Assignee:
            eliot Eliot Horowitz (Inactive)
            Reporter:
            geoffeg Geoffrey Gallaway
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: