Info

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.

Top User Comments

xgen-internal-githook commented on Thu, 22 Jun 2017 21:14:29 +0000: Author: {u'username': u'tessavitabile', u'name': u'Tess Avitabile', u'email': u'tess.avitabile@mongodb.com'} Message: SERVER-29798 Ensure 3.4 secondary replicates featureCompatibilityVersion document in set_feature_compatibility_version.js Branch: master https://github.com/mongodb/mongo/commit/19fb2eca839609a0b6d34faa11daee381f4eeff4

Steps to Reproduce