Since FCV does consensus through the oplog, it might be possible for a recipient node to be stuck in an upgrade/downgrade if it is split before it hears that the FCV operation is complete. After discussion with Cloud, we have decided to reject setFeatureCompatibilityVersion commands if there is an active shard split operation since the Cloud code to run FCV changes is resilient to transient failure.