-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Internal Code
-
None
-
Fully Compatible
-
ALL
-
Query 2017-07-10
-
0
Since the secondary has no votes, "majority" for the replica set equals 1, so the secondary need not receive the featureCompatibilityDocument for the setFeatureCompatibilityVersion command to succeed. In this case, the primary closes the connection to the secondary, and it spins, outputting the error message "IncompatibleServerVersion". We should give the secondary votes, so that the write is required to reach the secondary.