[SERVER-5347] getMore: cursor ScopedDbConnection: _conn != null Created: 21/Mar/12  Updated: 06/Dec/22  Resolved: 22/Feb/18

Status: Closed
Project: Core Server
Component/s: Querying, Sharding
Affects Version/s: 2.0.3
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Steffen Assignee: [DO NOT USE] Backlog - Sharding Team
Resolution: Done Votes: 2
Labels: mongos, sharding
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
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


Assigned Teams:
Sharding
Operating System: Linux
Participants:

 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


Generated at Thu Feb 08 03:08:37 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.