[SERVER-23110] dbeval with 'nolock' option checks for sharding metadata without collection lock Created: 14/Mar/16  Updated: 14/Apr/16  Resolved: 15/Mar/16

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 3.3.4

Type: Bug Priority: Major - P3
Reporter: Kaloian Manassiev Assignee: Kaloian Manassiev
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
Operating System: ALL
Sprint: Sharding 11 (03/11/16), Sharding 12 (04/01/16)
Participants:
Linked BF Score: 0

 Description   

dbeval cannot be run on sharded collections and there are checks to prevent that. However when it is run with the 'nolock' option it will perform this check without holding collection lock, which causes invariant failure on debug builds.



 Comments   
Comment by Githook User [ 15/Mar/16 ]

Author:

{u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}

Message: SERVER-23110 dbeval should not access collection sharding state
Branch: master
https://github.com/mongodb/mongo/commit/6210410de52b7695ffd2415ee2f1dea0374d24b2

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