[SERVER-1726] drop/dropDatabase concurrency when sharded Created: 03/Sep/10  Updated: 12/Jul/16  Resolved: 09/Aug/11

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

Type: Bug Priority: Major - P3
Reporter: Eliot Horowitz (Inactive) Assignee: Greg Studer
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-2253 db.dropDatabase is not erasing the da... Closed
is depended on by SERVER-3393 Dropping a sharded collection and re-... Closed
Related
Operating System: ALL
Participants:

 Comments   
Comment by Greg Studer [ 09/Aug/11 ]

Related to all sorts of other issues too, is the problem.

Comment by Greg Studer [ 09/Aug/11 ]

Partial fix for segfaults, fuller fix in 2.x?

Comment by auto [ 28/Jul/11 ]

Author:

{u'login': u'gregstuder', u'name': u'gregs', u'email': u'greg@10gen.com'}

Message: some test case fixes for SERVER-1726
Branch: master
https://github.com/mongodb/mongo/commit/d6cce7e211a45dbb1962c8c750f9d98e35bae897

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