Set featureCompatibilityVersion taking a very long time


I’ve been waiting for my cluster to finish changing the featureCompatibilityVersion. It’s been stuck in this state for 72 hours now:

        "featureCompatibilityVersion" : {
                "version" : "3.6",
                "targetVersion" : "4.0"
        "ok" : 1,
        "operationTime" : Timestamp(1625998757, 92),
        "$clusterTime" : {
                "clusterTime" : Timestamp(1625998757, 92),
                "signature" : {
                        "hash" : BinData(0,"AAAAAAAAAAAAAAAAAAAAAAAAAAA="),
                        "keyId" : NumberLong(0)

The system has a large amount of data, is it normal for it to take this long, though?

Two days later it’s still in the same state. I don’t know what to do about this…

I do not know why you do not get an error when running the command but targetVersion 4.0 is not valid for version 3.6.

If you think about, you are running version 3.6. The code for 4.0 does not exist yet. You can have a new server acts like an old one, but not the other way around.


1 Like

how long did it take to finish?
i also have the same problem, on the a db of size 2.9 TB.

24 hours and the command is still not finished.