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

getMore: cursor ScopedDbConnection: _conn != null

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Gone away
    • Affects Version/s: 2.0.3
    • Fix Version/s: None
    • Component/s: Querying, Sharding
    • Labels:
    • Environment:
      Linux 2.6.32-38-server, Ubuntu 10.04, MongoDB 2.0.1, 4 shards each Replicaset with 3 or more Nodes, NUMA, 2x XEON E5620 , 24 GB RAM
    • Operating System:
      Linux

      Description

      If we run a simple query on a sharded collection it failes after the reads have finished the first shard.

      we can reproduce it with:

      Javascript test query as file "script":
      function logi(pub) {
      print(new Date());
      print(pub.someId);
      };

      db.collection.find().forEach(logi);

      log output from this script with command "mongo refind < script ; date":
      Wed Mar 21 2012 17:21:23 GMT+0000 (UTC)
      NumberLong(1836664)
      Wed Mar 21 2012 17:21:23 GMT+0000 (UTC)
      NumberLong(1836859)
      Wed Mar 21 2012 17:21:23 GMT+0000 (UTC)
      NumberLong(1836883)
      Wed Mar 21 2012 17:21:23 GMT+0000 (UTC)
      undefined
      getMore: cursor didn't exist on server, possible restart or timeout?
      Wed Mar 21 17:21:23 UTC 2012

      log output router which we connect to:
      Wed Mar 21 17:21:23 [conn11974] ~ScopedDbConnection: _conn != null
      Wed Mar 21 17:21:23 [conn11974] end connection 127.0.0.1:12880

        Attachments

          Activity

            People

            Assignee:
            backlog-server-sharding Backlog - Sharding Team
            Reporter:
            steffen Steffen
            Participants:
            Votes:
            2 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: