[SERVER-4722] possible for partially returned results to be deleted by migrate cleanup Created: 19/Jan/12  Updated: 11/Jul/16  Resolved: 30/Jan/12

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 2.1.0
Fix Version/s: 2.1.0

Type: Bug Priority: Major - P3
Reporter: Greg Studer Assignee: Greg Studer
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File cursors_on_migrate.js     File query_on_migrate.js    
Operating System: ALL
Participants:

 Description   

See:

http://buildbot.mongodb.org:8081/builders/Linux%2064-bit%20v8/builds/2931/steps/test_3/logs/stdio

The results not returned in the first cursor batch are deleted by the cleanup immediately before the error.



 Comments   
Comment by auto [ 25/Feb/12 ]

Author:

{u'login': u'astaple', u'name': u'Aaron', u'email': u'aaron@10gen.com'}

Message: SERVER-4150 SERVER-4722 check for stale sharding config
Branch: master
https://github.com/mongodb/mongo/commit/5c0db4208cf8b0c4ce051190a4f93a17335ea21e

Comment by Greg Studer [ 26/Jan/12 ]

@eliot - took over b/c easier for me to track this way. Let me know if you want it back

Comment by Greg Studer [ 24/Jan/12 ]

New test that shows cursor growth after a number of migrations. Migrate alone does not cause this.

Comment by auto [ 23/Jan/12 ]

Author:

{u'login': u'erh', u'name': u'Eliot Horowitz', u'email': u'eliot@10gen.com'}

Message: if sharding metadata changes mid initial query reject and retry SERVER-4722
test forthcoming
Branch: master
https://github.com/mongodb/mongo/commit/52cd3d34a8db1ff28a07b0d27ff879a47a4f9c60

Comment by Greg Studer [ 19/Jan/12 ]

Test case should reproduce. What is required is a long query, but also one that does not return all results in the first batch, the data not returned in this batch is what is deleted.

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