Atlas M2 Cluster updated over night to v6 broke running

Overnight, Atlas to v6.0.5 and broke
our app completely (its not usable without db connection, even if all errors handled properly).

It seems latest mongodb Node client v5.2.0 is not supporting the breaking changes:

https://www.mongodb.com/docs/manual/legacy-opcodes/#op_query

We cannot change cluster version as we are using M2 instances.

1 Like

Hi @Elis,

Could you contact the Atlas in-app chat support team regarding this? Please provide them with the errors you’re receiving as well.

Regards,
Jason

1 Like

Same exact issue here since we’re using some op_query as well with mongoose version 5.X.X. Are you able to solve the problem? I tried to upgrade to mongoose 6.x.x but too many errors to deal with.

1 Like

It would be best to create a new post with the exact details/errors. However, in saying so, there were some email(s) sent out several months ago advising to test the new version and included some details on what to do with regards to the upgrade. Refer to also the relevant change notes for 6.0 and Legacy Opcodes.

1 Like