We are exposing in-progress transactions in the oplog for large transactions. Due to the requirement of Oplog Maintenance, it becomes necessary to expose the entire lifetime of transactions, including abort, to secondaries. Thus we need to always write an abort oplog entry whenever an in-progress unprepared transaction with replicated operations is aborted. Prepared transactions are already aborted with an oplog entry.