Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Oplog inconsistent after using dropDatbase #3847
Fringe scenario I've run into. I'm experimenting with mongo's
Moreover, if I try to re-insert old documents after the dropDatbase, I get the following error:
I assume this is because Meteor thinks that the documents were never removed.
There are a couple of solution I can think of, which I'm pursuing right now:
Any pointers would be appreciated.
referenced this issue
Mar 2, 2015
Good call. We currently do specially look for "drop collection" messages in the oplog, but not for "drop database" messages.
It would be great if you could follow our guidelines for reporting bugs and include an easy-to-test reproduction: https://github.com/meteor/meteor/wiki/Contributing-to-Meteor#reporting-a-bug-in-meteor
(Note that the answer in your link doesn't seem to have anything to do with "drop collection" vs "drop database" but just with "drop database" vs "remove all" --- ie, the fact that when you drop something the indices go away.)
I've put together a reproduction here: https://github.com/hitchcott/meteor-issue-3847
At first I tried something like this on the server:
But that worked as expected. So it seems the problem is limited to updating clients rather than the entire app being unaware of the