[SERVER-1817] A collection exists but the field "dropped" in "config.collections" is true Created: 21/Sep/10  Updated: 12/Jul/16  Resolved: 26/Sep/10

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 1.6.2
Fix Version/s: 1.7.1

Type: Bug Priority: Major - P3
Reporter: Che-Ching Wu Assignee: Alberto Lerner
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-1849 Recreating recently dropped collectio... Closed
depends on SERVER-1836 printSharding status showing "<ns> ch... Closed
Operating System: ALL
Participants:

 Description   

Please follow this steps:

use config
db.collections.find()
use admin
db.runCommand(

{enablesharding: "ching"}

)
db.runCommand({shardCollection: "ching.stew", key: {"_id":1}})
use ching
db.dropDatabase()
use admin
db.runCommand(

{enablesharding: "ching"}

)
db.runCommand({shardCollection: "ching.stew", key: {"_id":1}})
use config
db.collections.find()
use ching
show collections



 Comments   
Comment by Alberto Lerner [ 27/Sep/10 ]

This issue was solved by SERVER-1836 and SERVER-1849. They were both backported to 1.6.x. You could pick them up using the 1.6 nightly or on 1.6.4

Comment by Che-Ching Wu [ 27/Sep/10 ]

Would you please also fix this in 1.6.x?

Comment by Alberto Lerner [ 26/Sep/10 ]

Author:

{'login': 'alerner', 'name': 'Alberto Lerner', 'email': 'alerner@10gen.com'}

Message: SERVER-1849 allow recreating a recently dropped collection
http://github.com/mongodb/mongo/commit/e8f0119c5546f9133709ef82b42a1947f66aa494

Comment by Eliot Horowitz (Inactive) [ 26/Sep/10 ]

Is this fixed already?

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