-
Type:
Task
-
Resolution: Won't Fix
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Internal Code
-
None
-
Storage 2017-10-02
-
0
In SERVER-29350, we modify mongod to return supported wire versions (6,6) when receiving an isMaster command from an internalClient when the featureCompatibilityVersion is 3.6.
As a result, when starting a new replica set with a 3.6 primary and a 3.4 secondary, the secondary spins, logging:
remote host has incompatible wire version: IncompatibleServerVersion: Server min and max wire version are incompatible (6,6) with client min wire version (0,5)
Instead, the processes should quickly exit with a non-zero exit code and a useful error message. The error message should display a "MustUpgrade" error code and should link to the documentation for the 3.4=>3.6 upgrade process.
- depends on
-
-
- Closed
-
- is related to
-
SERVER-30920 Starting MongoDB 3.4 where previously collections were created with FCV 3.6 result in an abort.
-
- Closed
-
- related to
-
-
- Closed
-
-
SERVER-32633 Provide a framework to ensure a last-stable binary version node in a latest featureCompatibilityVersion replica set detects it has become isolated from a majority for all last stable binary versions >= 3.8 and crashes upon this detection
-
- Closed
-
-
SERVER-31094 Mongos should fail gracefully when pointing to a featureCompatibilityVersion 3.6 cluster
-
- Closed
-