Index builds use temporary record stores, which are not supposed to track size adjustments (and check inReplicationRecovery). On resume, the temporary record stores are opened using the regular record store code path, causing them to track size adjustments.

inReplicationRecovery is set to true in recoverFromOplog, but concurrent checks for inReplicationRecovery can be running before the recovery thread reaches that point. This is the case for index builds, which are restarted/resumed earlier in the recovery process, when rolling back the storage engine to the stable timestamp and re-opening the catalog (_recoverToStableTimestamp). This creates a race between an index build thread checking inReplicationRecovery and the rollback thread setting the flag.