I’m a little confused about how safe an upgrade from v6 to v7 (and after to v8).

I have dev Cluster0 8.0.4 (shared), and looks like my code is working correctly.

And I have production Cluster1 version: 6.0.20, Cluster Tier: M10 (General), Encrypted Storage: True.

Does it mean my code is already compatable with 7.0 / 8.0.4?

How to make this upgrade?

mongoose now is 7.0, connect-mongo: ^5.1.0.

I event can’t understand what instruction should use

Is it replica set?

I also found some configuration in cluster config:

image1187×281 14.7 KB

p.s never did upgrade for mongo, so a little afraid of do any change for real env.

just in details. from doc:

Check Driver Compatibility

Before you upgrade MongoDB, check that you’re using a MongoDB 7.0-compatible driver. Consult the driver documentation for your specific driver to verify compatibility with MongoDB 7.0.

Upgraded deployments that run on incompatible drivers might encounter unexpected or undefined behavior.

What is this mongodb7.0 driver? How to understand what is my current driver?

Compatibility Changes in MongoDB 7.0

1. storageDetails - do not use
2. FreeMonitoring - do not understand what is it, but look like do not use
3. Queryable Encryption General Availability - have no idea what is it

Backward-Incompatible Features

1. Collections with encryptedFields with [range indexes] - Have no idea what is it, but look like I don’t use it
2. Compound wildcard indexes require FCV 7.0 or greater. A pre-7.0 mongod does not start if you are using one or more compound wildcard indexes. - What is it?
3. Config servers that have collections with changeStreamPreAndPostImages enabled - have no idea what is it, but I think I don’t use it
4. Secondary TTL indexes with [partial filters] (https://www.mongodb.com/docs/manual/core/index-partial/#std-label-index-type-partial) on [time series collections] (https://www.mongodb.com/docs/manual/core/timeseries-collections/#std-label-manual-timeseries-collection) - can’t understand ttl but i have partial, but doesn’t have time searias
5. Time series collections with custom bucketing parameters - I hope I don’t use it

Have no idea what is it:

Intra-Node Authentication

Starting in MongoDB 7.0, you can configure servers to authenticate X.509 certificates as cluster members identified by attributes or extension values. You can also override this configuration to accept alternate certificates during a rolling upgrade.

What is it not clear too:

Cluster Configuration

Active setClusterParameter parameter operations prevent feature Compatibility Version (FCV) from successful completion.