drop database error

[fanbreeze]

I have databases: buy, buy_201107, buy_201108

buy's collections: mytest

buy_201107 and buy_201108 collections: data, data.chunks, data.files

there are a lot of data in buy and buy_201107. buy_201108 is empty;

when I ran command: "use buy, db.dropDatabase()", I found that
buy_201107 was dropped, but buy_201108 was not dropped.

I don't know why

the following is mongos' log:

Sat Jul 23 23:49:38 [conn663642] DROP DATABASE: buy
Sat Jul 23 23:49:38 [conn663642] DBConfig::dropDatabase: buy
Sat Jul 23 23:49:39 [conn663642] about to log metadata event: { _id:
"mg03-2011-07-23T15:49:38-0", server: "mg03", clientAddr: "N/A", time:
new Date(1311436179027), what: "dropDatabase.start", ns: "buy",
details: {} }
Sat Jul 23 23:49:39 [conn663642] about to log metadata event: { _id:
"mg03-2011-07-23T15:49:39-1", server: "mg03", clientAddr: "N/A", time:
new Date(1311436179091), what: "dropCollection.start", ns:
"buy_201107.data", details: {} }
Sat Jul 23 23:49:39 [conn663642] about to log metadata event: { _id:
"mg03-2011-07-23T15:49:39-2", server: "mg03", clientAddr: "N/A", time:
new Date(1311436179218), what: "dropCollection", ns:
"buy_201107.data", details: {} }
Sat Jul 23 23:49:39 [conn663642] about to log metadata event: { _id:
"mg03-2011-07-23T15:49:39-3", server: "mg03", clientAddr: "N/A", time:
new Date(1311436179242), what: "dropCollection.start", ns:
"buy_201107.data.chunks", details: {} }
Sat Jul 23 23:49:39 [conn663642] about to log metadata event: { _id:
"mg03-2011-07-23T15:49:39-4", server: "mg03", clientAddr: "N/A", time:
new Date(1311436179429), what: "dropCollection", ns:
"buy_201107.data.chunks", details: {} }
Sat Jul 23 23:49:39 [mongosMain] connection accepted from
192.168.8.187:40511 #663876
Sat Jul 23 23:49:39 [conn663875] end connection 192.168.8.187:40511
Sat Jul 23 23:49:39 [conn663642] about to log metadata event: { _id:
"mg03-2011-07-23T15:49:39-5", server: "mg03", clientAddr: "N/A", time:
new Date(1311436179443), what: "dropCollection.start", ns:
"buy_201107.data.files", details: {} }
Sat Jul 23 23:49:39 [conn663642] about to log metadata event: { _id:
"mg03-2011-07-23T15:49:39-6", server: "mg03", clientAddr: "N/A", time:
new Date(1311436179562), what: "dropCollection", ns:
"buy_201107.data.files", details: {} }
Sat Jul 23 23:49:39 [conn663642] DBConfig::dropDatabase: buy
dropped sharded collections: 3
Sat Jul 23 23:49:39 [conn663642] DBConfig::dropDatabase: buy
dropped sharded collections: 0
Sat Jul 23 23:49:39 [mongosMain] connection accepted from
192.168.8.186:37763 #663877
Sat Jul 23 23:49:39 [conn663876] end connection 192.168.8.186:37763
Sat Jul 23 23:49:41 [WriteBackListener] MessagingPort say send() errno:
32 Broken pipe 192.168.8.91:20000
Sat Jul 23 23:49:41 [WriteBackListener] query failed to:
192.168.8.91:20000 exception
Sat Jul 23 23:49:41 [WriteBackListener] MessagingPort say send() errno:
32 Broken pipe 192.168.8.182:20000
Sat Jul 23 23:49:41 [WriteBackListener] query failed to:
192.168.8.182:20000 exception
Sat Jul 23 23:49:41 [WriteBackListener] MessagingPort say send() errno:
32 Broken pipe 192.168.8.184:20000
Sat Jul 23 23:49:41 [WriteBackListener] query failed to:
192.168.8.184:20000 exception
Sat Jul 23 23:49:41 [WriteBackListener] ~ScopedDBConnection: _conn !=
null
Sat Jul 23 23:49:41 [WriteBackListener] ERROR: error processing
writeback: 8002 all servers down!
Sat Jul 23 23:49:41 [conn663642] about to log metadata event: { _id:
"mg03-2011-07-23T15:49:41-7", server: "mg03", clientAddr: "N/A", time:
new Date(1311436181022), what: "dropDatabase", ns: "buy", details:
{} }

[Alvin Richards]

I have added the following ticket to track this

https://jira.mongodb.org/browse/SERVER-3471

Which version were you using and can you confirm that there was just a
single 'db.dropDatabase()' being executed?

Also, you used this command "use buy, db.dropDatabase()". This
switches to the database "buy, db.dropDatabase()". Can you confirm the
command you executed.

-Alvin

[fanbreeze]

the version is 1.8.2, I can confirm that I just ran the command

On 7月25日, 下午6时46分, Alvin Richards <alvin.richa...@gmail.com> wrote:
> I have added the following ticket to track this
>
> https://jira.mongodb.org/browse/SERVER-3471
>
> Which version were you using and can you confirm that there was just a
> single 'db.dropDatabase()' being executed?
>
> Also, you used this command "use buy, db.dropDatabase()". This
> switches to the database "buy, db.dropDatabase()". Can you confirm the
> command you executed.
>
> -Alvin
>
> On Jul 25, 8:46 am, fanbreeze <fanbre...@gmail.com> wrote:
>
>
>
>
>
>
>
> > I have databases: buy, buy_201107, buy_201108
>
> > buy's collections: mytest
>
> > buy_201107 and buy_201108 collections:data,data.chunks,data.files
>

> > there are a lot ofdatain buy and buy_201107. buy_201108 is empty;

>
> > when I ran command: "use buy, db.dropDatabase()", I found that
> > buy_201107 was dropped, but buy_201108 was not dropped.
>
> > I don't know why
>
> > the following is mongos' log:
>

> > Sat Jul 23 23:49:38 [conn663642]DROPDATABASE: buy