"collection's metadata is undergoing changes. Please try again."

[Zach Smith]

I'm attempting to drop a sharded collection and I keep receiving this error:

Wed Oct 26 14:45:46 uncaught exception: drop failed: {

"assertion" : "collection's metadata is undergoing changes. Please try again.",

"assertionCode" : 13331,

"errmsg" : "db assertion failure",

"ok" : 0

}

I've tried again many times, but with no luck. Any thoughts on debugging this? I'm thinking this may also be related to the fact that this collection isn't balancing properly.  It currently has 26 chunks on one shard and only 1 on the other.

Thanks for the help. 

[Nat]

Can you check mongos,mongod log? There might be other previous exceptions/assertions.

[Zach Smith]

The problems both seems to have fixed themselves. I connected to the primary mongod process in one of the replicasets and queried it directly. This caused it to crash, but then when a new instance took over the the primary, everything worked itself out.

I can't get to the old log files because apparently mongo overwrites the log file from a previous run rather than appending to it.

A bit confused about what happened, but at least everything is working now. 

On Wed, Oct 26, 2011 at 11:06 AM, Nat <nat....@gmail.com> wrote:

Can you check mongos,mongod log? There might be other previous exceptions/assertions.

--
You received this message because you are subscribed to the Google Groups "mongodb-user" group.
To view this discussion on the web visit https://groups.google.com/d/msg/mongodb-user/-/VSn8XkQ3VrcJ.
To post to this group, send email to mongod...@googlegroups.com.
To unsubscribe from this group, send email to mongodb-user...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/mongodb-user?hl=en.