Thanks for the quick response @sashko. Your answer still leaves two open questions:
When is MDG switching also in deployment mode to Mongo 3.0 or even 3.2? I quote from the above blog article: “Meteor ships with MongoDB 2.6; we will keep a close eye on the maturation of MongoDB 3.0 and transition to it as the default MongoDB engine in a future release.”
Where can I find documentation on how to install MongoDB 3.0 in deployment and also in production mode?
Thanks
I assume you mean “development” mode? If so, I don’t know right now. If you’re really into using MongoDB 3.2 locally, follow the below directions:
MONGO_URL=mongodb://localhost:27017/<your_db_name> meteor
Should just work. Note that this is exactly what you would need to do to run Mongo with a regular Node app.
Plus turning on oplog and another environmental variable to use oplog too.
If I remember correctly.
You should only really need that in production. You can read some of Arunoda’s blog posts about how to turn that stuff on; we’ll also have it in the guide.
Ok, made the jump. Wasn’t too difficult (apart from learning about Brew
which I didn’t knew before). I didn’t know if I need SSL for my local
MongoDB so I was installing it without first.
Thanks again for pointing me in the right direction, @sashko
what about npm-mongo driver? the current 1.4.x version doesn’t seem to be compatible with MongoDB 3.2
https://docs.mongodb.org/ecosystem/drivers/driver-compatibility-reference/#reference-compatibility-mongodb-node
Using mongo@1.1.0 without any problems. All works fine, it’s running faster and I’m still at 0.001 GB for the database
Resurrecting this thread like a necromancer raises the undead.
It would be great if Meteor used MongoDB 3.x in dev mode. Any particular reason it still uses 2.6.7?
@ffxsam Meteor 1.4 uses MongoDB 3.2 (in both dev and production), the beta process should be starting early next week.
That’s great news! Thanks for the info.
I try in windows 7, but show
~MONGO_URL is don’t reconigzed~
Last necrobump, I promise, but it deserves attention from everyone who participated in any discussion around this topic. Loving MDG team, please update the default Mongo to 3.4+, which fixes the infamous data-consistency bug. This reason alone is a strong reason to update!
Oh! Apparently I need to read the blog more: the updates are coming!
Nonetheless, the hordes raised from the dead are good, so people can know what light is coming.
Why are we still at MongoDB version 3.2.15?
I have a great need for NumberDecimal which MongoDB had released in version 3.4.
Mongo 3.4 support is coming in Meteor 1.6.1 (see https://github.com/meteor/meteor/pull/9396). The changes have already been merged, and 1.6.1 will be coming soon (we still have a few release candidate bugs to squash).
Thanks hwillson! Can you tell when you’ll support the current 3.6?
Meteor 1.6.1 is now feature locked, so after it’s released we’ll start looking at Mongo 3.6. We’ll try to get Mongo 3.6. support into 1.6.2 (excluding the use of Mongo 3.6 change streams in Meteor - that’s a bigger issue, that will definitely take more time to explore).
As the OP, I can let everyone know that we are running 3.6.1 in our production system without any problem.
The upgrade was seamless but please note that we are hosting on Atlas, so the experience might be different on other hosting providers.
We’re on 3.6.5 now without problems, all working well with WT. When we’re on 4.0 I will let you guys know how it went.
If anyone goes down that path soon, please update us here as well.
Thanks