If the primary has featureCompatibilityVersion 3.4, and during initial sync, we copy over decimal data before copying admin.system.version, then we reject the decimal data, and the initial sync fails.
We would also like to successfully initial sync from a primary with featureCompatibilityVersion 3.2 that has decimal data, since a user can get into this state by inserting decimal data and then setting featureCompatibilityVersion to 3.2.
- has to be done before
-
SERVER-25725 Running {setFeatureCompatibilityVersion: "3.4"} on a 3.4 primary should kill 3.2 secondaries
-
- Closed
-
- related to
-
SERVER-25131 CollectionBulkLoaderImpl should release locks on task errors
-
- Closed
-