Summary:
 
The version field in MongoDB replica sets is incremented on each reconfiguration. However, when this field reaches its maximum value of Int32 (2,147,483,647), it prevents further reconfigurations, leading to operational issues.

Detailed Description

During a resiliency/failover scenario , we have been experiencing mongo dbPath growing because of the WiredTigerHS.wt file outlined in SERVER-84108

. So whenever such situation happens we remove the member from the replicaSet or reduce the priority and votes to 0. While doing this we have to use force option as recommended by mongo in https://www.mongodb.com/docs/v4.4/tutorial/reconfigure-replica-set-with-unavailable-members/.

As per Mongo when the force option is used, Mongo will increment the version by large number in 100,000s. But once the replicaSet version reaches the max Value, it wont be able to accept anymore reconfig.  

• what is the way to recover the replicaSet when the version reaches its max Value??
• Do we really need to increment the version by this larger value?? Is there a way to reduce the version update not by 100,000 but some lesser number when force option is used?