SERVER-60869 Re-add logic to set feature compatibility version on arbiters

(cherry picked from commit f094005b0b8a878bc039ddae540b8696f70848f7)

1 files changed, 9 insertions, 0 deletions

diff --git a/src/mongo/db/repl/replication_coordinator_impl.cpp b/src/mongo/db/repl/replication_coordinator_impl.cpp
index e9893df98e4..376661d929e 100644
--- a/src/mongo/db/repl/replication_coordinator_impl.cpp
+++ b/src/mongo/db/repl/replication_coordinator_impl.cpp
@@ -4301,6 +4301,15 @@ ReplicationCoordinatorImpl::_updateMemberStateFromTopologyCoordinator(WithLock l
           "Replica set state transition",
           "newState"_attr = newState,
           "oldState"_attr = _memberState);
+
+    // Initializes the featureCompatibilityVersion to the latest value, because arbiters do not
+    // receive the replicated version. This is to avoid bugs like SERVER-32639.
+    if (newState.arbiter()) {
+        // (Generic FCV reference): This FCV check should exist across LTS binary versions.
+        serverGlobalParams.mutableFeatureCompatibility.setVersion(
+            FeatureCompatibilityParams::kLatest);
+    }
+
     _memberState = newState;
 
     _cancelAndRescheduleElectionTimeout_inlock();