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

What exactly causes "can't find index in storeCurrentLocs"

    XMLWordPrintable

    Details

    • Type: Question
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Cannot Reproduce
    • Affects Version/s: 2.0.7
    • Fix Version/s: None
    • Component/s: Sharding
    • Labels:
      None

      Description

      Every now and then we run into errors like these :

      Fri Aug 10 11:29:38 [Balancer] moveChunk result:

      { errmsg: "can't find index in storeCurrentLocs", ok: 0.0 }

      Fri Aug 10 11:29:38 [Balancer] balancer move failed:

      { errmsg: "can't find index in storeCurrentLocs", ok: 0.0 }

      On top of that my config.mongos collection is slowly filling up with documents so those are not cleaned up (should they be?). For example I see 71 documents there while there are 20 mongos connected currently.

      Any idea what can cause these sorts of issues? Can killing mongos processes cause this for example?

        Attachments

          Activity

            People

            Assignee:
            spencer Spencer Brody (Inactive)
            Reporter:
            remonvv Remon van Vliet
            Participants:
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: