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

Sharded collection fails on "stats()" with "ns not found", but "find()" works.

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Incomplete
    • Affects Version/s: 2.4.8
    • Fix Version/s: None
    • Component/s: Sharding
    • Labels:
      None
    • Operating System:
      ALL
    • Steps To Reproduce:
      Hide

      Running 2.4.8.

      Show
      Running 2.4.8.

      Description

      We have created a temporary collection for the purposes of map-reduce output. After running several map-reduce jobs that failed in the last moment due to a networking error, we wanted to inspect the stats on those collections.

      About 30-50% of the collections fail on the "stats()" call but can be successfully iterated using "find()". I have also confirmed that the collections actually exist on every shard (by connecting to each shard's mongo and doing a stats() call there).

      mongos> db.collection_nw1q.stats()
      {
      	"sharded" : true,
      	"ok" : 0,
      	"errmsg" : "failed on shard: { ok: 0.0, errmsg: \"ns not found\" }"
      }
      mongos> db.collection_nw1q.find({}, {_id: 1}).sort({_id: 1}).limit(20)
      ... actual data returned here, no error ...

      There are no errors in mongos, even at logLevel: 1, when the failed stats() call returns.

        Attachments

          Activity

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            oleg@evergage.com Oleg Rekutin
            Participants:
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: