[SERVER-21835] Prevent CappedPositionLost workload failures with indexed_insert_base_capped.js Created: 10/Dec/15  Updated: 16/Nov/16  Resolved: 21/Dec/15

Status: Closed
Project: Core Server
Component/s: Testing Infrastructure
Affects Version/s: 3.2.0
Fix Version/s: 3.2.1, 3.3.0

Type: Bug Priority: Major - P3
Reporter: Kamran K. Assignee: Max Hirschhorn
Resolution: Done Votes: 0
Labels: test-only
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Completed:
Sprint: QuInt E (01/11/16)
Participants:
Linked BF Score: 0

 Description   

The indexed_insert_base_capped.js FSM workload can fail with this error if a yield occurs during a collection scan and the position becomes invalidated by a deletion from the capped collection:

        Error: error: {
        	"waitedMS" : NumberLong(0),
        	"ok" : 0,
        	"errmsg" : "Executor error during find command: CappedPositionLost CollectionScan died due to position in capped collection being deleted. Last seen record id: RecordId(0)",
        	"code" : 96
        }



 Comments   
Comment by Githook User [ 21/Dec/15 ]

Author:

{u'username': u'visemet', u'name': u'Max Hirschhorn', u'email': u'max.hirschhorn@mongodb.com'}

Message: SERVER-21835 Ignore errors due to CappedPositionLost in make_capped.js.

(cherry picked from commit 9736f7439eda1f6a7856c535683fda239be86e04)
Branch: v3.2
https://github.com/mongodb/mongo/commit/1dfd2cffcf1dc0cc49fe37e0f98daf8d464e0a5e

Comment by Githook User [ 21/Dec/15 ]

Author:

{u'username': u'visemet', u'name': u'Max Hirschhorn', u'email': u'max.hirschhorn@mongodb.com'}

Message: SERVER-21835 Ignore errors due to CappedPositionLost in make_capped.js.
Branch: master
https://github.com/mongodb/mongo/commit/9736f7439eda1f6a7856c535683fda239be86e04

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