In preparation of WT-8747 it was discovered after applying the preliminary patch that there is potential for deadlocking the server with the following sequence of actions:

• Transaction A commits data with commit_timestamp=20,durable_timestamp=30
• Transaction B begins at timestamp 25 and attempts to read data, leading to a WT_PREPARED_CONFLICT as A has not yet been made durable and waiting until another transaction commits or aborts.{{}}
• Transaction B is deadlocked if there are no more transactions happening

To avoid this a solution is to add a timeout mechanism that will retry the method even if a transaction has not yet been committed/rolled back so that it can pick up eventually when the data has been made durable.