MongoDB 5.0 is out

core
21

Meteor 2.6 is already out (it’s going to be recommended soon) and it adds the support to MongoDB 5.x.

The migration guide is here.

1 Like
22

I’m assuming you run this on the admin database.

If so, what privileges have you added to the db user?

I’m getting the following after adding a number of roles:
Atlas atlas-hu2kj6-shard-0 [primary] admin> db.adminCommand( { setFeatureCompatibilityVersion: “4.4” } )
MongoServerError: not authorized on admin to execute command { setFeatureCompatibilityVersion: “4.4”, lsid: { id: UUID(“4748e0c5-6963-42f7-b500-6e7400b90b5c”) }, $clusterTime: { clusterTime: Timestamp(1644688103, 1), signature: { hash: BinData(0, 7F3DF7CA04D2088597B29752464D8DAD7DA24433), keyId: 7063867780415619076 } }, $db: “admin” }

23

Just a small update to this conversation. At this time, I can see my M0 cluster in Atlas is running MongoDB 5.0.6 Enterprise and I have no issues with Meteor 2.6.0. I don’t use redis-oplog and I use grapher.

3 Likes
24

I had major troubles after updating to meteor 2.6! After hours I found that the mongo package was not updated to the latest version with some important fixes. I updated the mongo package from 1.14.0 to 1.14.5, now everything works perfect again.

1 Like
25

Hi, I’m currently having the same issue. Have you found a way around it? Can’t upgrade to meteor 2.6 (currently on 2.1) as it involves a lot of additional refactoring. But right now I’m having the same issue with Mongo 5.0 on Atlas highlighted in this thread.