There is a bug in MongoDB with reconstructing prepared transactions at startup (see SERVER-58409 for details). We discovered that the simplest solution would be to have MongoDB set the read timestamp to the prepare timestamp on startup to ensure that the first write into the RecordStore does not re-use a RecordId for a deleted record.

The proposed MongoDB change, however, exercises the following assertion: "prepare timestamp X must be greater than the latest active read timestamp Y".

We would like some API to bypass this assertion. daniel.gottlieb proposed an API change that would allow the configuration "roundup_timestamps=(prepared=true)" to bypass this assertion. We set this flag already when we recover prepared transactions on startup.