How to fix TransactionExceededLifetimeLimitSeconds: Transaction exceeded lifetime limit in MongoDB

Split large batches of reads or writes into separate transactions so each one finishes well before 60 seconds. For example, commit after every few hundred documents instead of wrapping the entire job in a single transaction:

const session = client.startSession();
try {
  await session.withTransaction(async () => {
    for (const chunk of chunks) {
      await collection.insertMany(chunk, { session });
    }
  });
} finally {
  await session.endSession();
}

Chunk the array or cursor data so the loop above can finish quickly rather than holding the transaction open for its entire duration.

Use db.currentOp({ active: true, "transaction.state": { $exists: true } }) to spot transactions that approach the lifetime limit. Ensure the commands inside the transaction use covering indexes, keep network calls outside the transaction, and add maxTimeMS if you can bail early:

await db.collection("orders")
  .find({ status: "pending" })
  .maxTimeMS(2000)
  .toArray();

If a read or write takes too long, finish the transaction, diagnose the slow query, and try to optimize it before retrying.

Set the transactionLifetimeLimitSeconds server parameter when the workload legitimately needs more time, but do so carefully so long-lived transactions do not block the cluster:

// Once per replica set
await db.adminCommand({
  setParameter: 1,
  transactionLifetimeLimitSeconds: 120,
});

Or start mongod with:

mongod --setParameter transactionLifetimeLimitSeconds=120

Atlas clusters expose this parameter under the Advanced Configuration section. Always monitor locks and replication lag after raising the limit because each transaction can now hold on to resources longer.