Transaction table updates may be applied out of order when retryable writes and transactions are in the same secondary batch

  load( "jstests/libs/write_concern_util.js" );   let rst = new ReplSetTest({nodes: 2}); rst.startSet(); rst.initiate();   let primary = rst.getPrimary(); let secondary = rst.getSecondary();   // Pause replication so ops are applied in a single batch on secondary. stopServerReplication(secondary);   const session = primary.getDB( "test" ).getMongo().startSession({causalConsistency: false }); const sessionDb = session.getDatabase( "test" ); const sessionColl = sessionDb[ "test" ];   // Create collection. sessionColl.insert({});   var k = 0; jsTestLog( "Running some retryable writes." ); for ( var i = 0; i < 5; i++) { assert.commandWorked(primary.getDB( "test" ).runCommand({ insert: 'user' , documents: [{x: k, retryableWrite: 1}], lsid: {id: session.getSessionId().id}, txnNumber: NumberLong(k) })); k++ }   jsTestLog( "Running some transactions." ); for ( var i = 0; i < 5; i++) { assert.commandWorked(sessionDb.runCommand({ insert: "test" , documents: [{x: k}], readConcern: {level: "snapshot" }, txnNumber: NumberLong(k), startTransaction: true , autocommit: false })); assert.commandWorked(sessionDb.adminCommand( {commitTransaction: 1, writeConcern: {w: 1}, txnNumber: NumberLong(k), autocommit: false })); k++ }   restartServerReplication(secondary); // expect db hash mismatch on 'config.transactions' rst.stopSet();