[SERVER-13130] db.upgradeCheck() or db.upgradeCheckAllDbs() can time out Created: 11/Mar/14  Updated: 11/Jul/16  Resolved: 12/Mar/14

Status: Closed
Project: Core Server
Component/s: Shell
Affects Version/s: 2.6.0-rc1
Fix Version/s: 2.6.0-rc2

Type: Bug Priority: Major - P3
Reporter: Andre de Frere Assignee: Matt Dannenberg
Resolution: Done Votes: 0
Labels: 26qa
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-8391 Pre-flight upgrade tool to check for ... Closed
Operating System: ALL
Participants:

 Description   

On a large database (or a number of large databases) db.upgradeCheck() can time out, leaving the user without a definitive response as to the status of their upgrade:

mongos> use admin
switched to db admin
mongos> db.upgradeCheckAllDbs()
...
...
23766468 documents processed
23804050 documents processed
23842477 documents processed
2014-03-11T00:41:55.871+0000 error: {
        "$err" : "getMore: cursor didn't exist on server, possible restart or timeout?",
        "code" : 13127
} at src/mongo/shell/query.js:131



 Comments   
Comment by Githook User [ 12/Mar/14 ]

Author:

{u'username': u'dannenberg', u'name': u'matt dannenberg', u'email': u'matt.dannenberg@10gen.com'}

Message: SERVER-13130 prevent upgradeCheck()'s cursors from timing out
Branch: master
https://github.com/mongodb/mongo/commit/456febf80507a12085771b803c4d475484e726d9

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