[SERVER-26367] index_killop.js should use failpoint rather than large collection to catch in-progress index build Created: 28/Sep/16  Updated: 19/Nov/16  Resolved: 03/Oct/16

Status: Closed
Project: Core Server
Component/s: Index Maintenance
Affects Version/s: None
Fix Version/s: 3.4.0-rc0

Type: Improvement Priority: Major - P3
Reporter: James Wahlin Assignee: James Wahlin
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Sprint: Integration 2016-10-10
Participants:
Linked BF Score: 0

 Description   

index_killop.js currently depends that indexing of a large collection will take sufficiently long to allow for capture of in-progress state via currentOp and to kill. We should use a failpoint instead to ensure that the index build is in progress.



 Comments   
Comment by Githook User [ 03/Oct/16 ]

Author:

{u'username': u'jameswahlin', u'name': u'James Wahlin', u'email': u'james.wahlin@10gen.com'}

Message: SERVER-26367 index_killop.js should use failpoint
Branch: master
https://github.com/mongodb/mongo/commit/ab912a90501ffa988591ab5173773b538cc22cac

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