Startup recovery adjusts the replSetMemberInStandaloneMode service context parameter several times, which causes a data race if an operation context is created on a background thread while this is happening. This specific race is harmless other than tripping tsan as the throughput probing job doesn't care about the value of this parameter.

An alternative solution would be to make the field atomic or lock access to it, but this could mask actual bugs related to reading it while it's being modified and seeing the incorrect value.