[SERVER-12728] Remove invalid gle call in removec.js test Created: 14/Feb/14  Updated: 11/Jul/16  Resolved: 14/Feb/14

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 2.6.0-rc0

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

Issue Links:
Related
related to SERVER-12716 removec.js failing in sharding passth... Closed
Operating System: ALL
Steps To Reproduce:

Create a new cursor in the shell, force a failure on the next getMore, ensure that an exception is thrown.

Participants:

 Description   

Original title: v8_db.cpp::internalCursorNext() does not use DBClientCursor::nextSafe()

Without using nextSafe(), iteration of DBClientCursors do not throw exceptions when getMore() fails, for instance, because they interpret the result as a valid final document of the form

{ $err : "message" }

.

This code should be audited to ensure that it throws the exception or is handled in a different way.



 Comments   
Comment by Githook User [ 14/Feb/14 ]

Author:

{u'username': u'renctan', u'name': u'Randolph Tan', u'email': u'randolph@10gen.com'}

Message: SERVER-12728 Remove invalid gle call in removec.js test
Branch: master
https://github.com/mongodb/mongo/commit/38e50fc06d6592e3e67257d7493416482a5d386d

Comment by Greg Studer [ 14/Feb/14 ]

removec.js should also be modified to not check GLE after find() once this behavior is fixed / confirmed correct.

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