[SERVER-40818] exhaust_cursor_currentop_integration_test should not drop getMore()'s read lock Created: 25/Apr/19  Updated: 29/Oct/23  Resolved: 26/Apr/19

Status: Closed
Project: Core Server
Component/s: Storage
Affects Version/s: None
Fix Version/s: 4.1.11

Type: Bug Priority: Major - P3
Reporter: Gregory Wlodarek Assignee: Gregory Wlodarek
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-40547 change handling of nextNotIncreasing ... Closed
Related
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Storage NYC 2019-05-06
Participants:
Linked BF Score: 21

 Description   

For SERVER-40547, when test commands are enabled, we crash if nextNotIncreasing instead of throwing a WriteConflictException.

With the work done in SERVER-40547, it uncovered a violation in the integration_tests_standalone_audit suite for the exhaust_cursor_currentop_integration_test test with the following message:

WTCursor::next -- c->next_key ( RecordId(1)) was not greater than _lastReturnedId (RecordId(2)) which is a bug.

Evergreen patch with SERVER-40547 changes.

resmoke.py invocation for local usage:

buildscripts/resmoke.py --suites=integration_tests_standalone_audit



 Comments   
Comment by Githook User [ 26/Apr/19 ]

Author:

{'email': 'gregory.wlodarek@mongodb.com', 'name': 'Gregory Wlodarek', 'username': 'GWlodarek'}

Message: SERVER-40818 exhaust_cursor_currentop_integration_test should not drop getMore()'s read lock
Branch: master
https://github.com/mongodb/mongo/commit/c97a46f335326fa89520cacfca8f54be8571f34a

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