[SERVER-4812] killcursor messages sent via piggyback data, which may be sent later or not at all Created: 30/Jan/12  Updated: 11/Jul/16  Resolved: 21/Feb/12

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

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 query_on_migrate.js    
Operating System: ALL
Participants:

 Description   

... solution is probably to send independently, as cursors building up can block migrations and overhead is minimal.



 Comments   
Comment by auto [ 19/Apr/12 ]

Author:

{u'login': u'gregstuder', u'name': u'Greg Studer', u'email': u'greg@10gen.com'}

Message: SERVER-4812 use say() not sayPiggyback() when closing cursors and lazyKill is false (i.e. in mongos)
Branch: v2.0
https://github.com/mongodb/mongo/commit/5f4961309049c5bef3b8669e7972a19d52ec85d3

Comment by auto [ 21/Feb/12 ]

Author:

{u'login': u'gregstuder', u'name': u'Greg Studer', u'email': u'greg@10gen.com'}

Message: SERVER-4812 use say() not sayPiggyback() when closing cursors and lazyKill is false (i.e. in mongos)
Branch: master
https://github.com/mongodb/mongo/commit/be99a7f6b315cf3e0c3e136977fb222494bfa5bd

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