Due to SERVER-102648, access to ShardingState is now restricted until it has been properly initialized. As a result, DatabaseShardingState fails during recovery because it tries to access the ShardId from ShardingState in the onConsistentDataAvailable method. This happens when reading from disk and installing the database metadata into DatabaseShardingState.

Within that method (specifically in setDbInfo), there's a validation that checks whether the ShardingState::ShardId matches the one in the DbVersion. This is not strictly necessary and is only a sanity check.

Therefore, I propose skipping this validation if ShardingState is not yet enabled—i.e., during recovery.