This call can throw WriteConflictException. Initially, I thought the invariantWTOK check below would invariant if the return code is WT_ROLLBACK. But apparently, invariantWTOK makes use of wtRCToStatus which still throws WriteConflictException on WT_ROLLBACK.

The function getLatestOplogTimestamp is called as part of the destructor of LastOpFixer. And so an uncaught WriteConflictException would crash the server as destructors are implicitly noexcept.

Either we should handle/retry this at the caller ReplicationCoordinatorImpl::getLatestWriteOpTime or inside WiredTigerRecordStore::getLatestOplogTimestamp, assuming replClientInfo().setLastOpToSystemLastOpTimeIgnoringCtxInterrupted(_opCtx) inside ~LastOpFixer is never called inside a bigger WT write transaction.