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

ClientCursor::staticYield can't unlock b/c of recursive lock ns

    • Type: Icon: Bug Bug
    • Resolution: Incomplete
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 2.6.6
    • Component/s: Querying
    • Labels:
      None
    • Environment:
      SSD drives
      CentOS 6.5
    • Linux
    • Hide

      it's intermittent and I can't replicate it. It's not even specific to times of heavy load.

      Show
      it's intermittent and I can't replicate it. It's not even specific to times of heavy load.

      Intermittently my logs fill with "ClientCursor::staticYield can't unlock b/c of recursive lock ns ..."[millions of entries] . It happens on a lot of different collections but always on a findAndModify. When it's at it's worse - the lock lasts 6-7 seconds but the entire database is unresponsive during this time.
      I've read that it may may be related to insufficient indexing but I've checked that with a .explain and the cursor is BtreeCursor.
      The issue is similar to this SERVER-15583
      but an upgrade to 2.6.6 solved his whereas I'm already on 2.6.6.

            Assignee:
            ramon.fernandez@mongodb.com Ramon Fernandez Marina
            Reporter:
            ricei Ian Rice
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: