# Transaction is too old to perform reads or be committed AND Request for future version

**URL:** <https://forums.foundationdb.org/t/transaction-is-too-old-to-perform-reads-or-be-committed-and-request-for-future-version/1857>\
**Category:** Using FoundationDB\
**Created:** [December 27, 2019, 4:56pm UTC](https://forums.foundationdb.org/t/transaction-is-too-old-to-perform-reads-or-be-committed-and-request-for-future-version/1857 "2019-12-27T16:56:33Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![nischalkumar](https://sea1.discourse-cdn.com/foundationdb/user_avatar/forums.foundationdb.org/nischalkumar/32/933_2.png) [@nischalkumar](https://forums.foundationdb.org/u/nischalkumar)\
**Post date:** [December 27, 2019, 4:56pm UTC](https://forums.foundationdb.org/t/transaction-is-too-old-to-perform-reads-or-be-committed-and-request-for-future-version/1857/1 "2019-12-27T16:56:33Z")

</div>

i am using foundation db as storage backend for janusGraph. I am facing two exceptions in general.

- Caused by: com.apple.foundationdb.FDBException: Transaction is too old to perform reads or be committed
- FDBException: Request for future version

What is the meaning of the above exceptions? How can I mitigate them?

---

<div class="post-metadata">

**Author:** ![alexmiller](https://sea1.discourse-cdn.com/foundationdb/user_avatar/forums.foundationdb.org/alexmiller/32/326_2.png) [@alexmiller](https://forums.foundationdb.org/u/alexmiller)\
**Post date:** [December 31, 2019, 12:22am UTC](https://forums.foundationdb.org/t/transaction-is-too-old-to-perform-reads-or-be-committed-and-request-for-future-version/1857/2 "2019-12-31T00:22:23Z")

</div>

There’s a number of threads that touch on these errors already.

#### Transaction too old

This is likely that janus graph is trying to issue reads within a transaction for longer than 5s.

- [Large Range Scans - avoid 5s limit](https://forums.foundationdb.org/t/large-range-scans-avoid-5s-limit/292)
- [What does it mean "Transaction Is Retryable", In particular to Handle Error of "Transaction Too Old"?](https://forums.foundationdb.org/t/what-does-it-mean-transaction-is-retryable-in-particular-to-handle-error-of-transaction-too-old/1451)

#### Request for future version

This is generally a sign of a slow storage server with many potential causes: write bandwidth saturation, an improperly configured cluster, large performance variations across processes. This is likely more related to cluster or workload setup/sizing than your exact client code.

- [High rate of transaction retries with error code 1009 (Request for future version)](https://forums.foundationdb.org/t/high-rate-of-transaction-retries-with-error-code-1009-request-for-future-version/1715)
- [FoundationDB error code 1009 (Request for future version)](https://forums.foundationdb.org/t/foundationdb-error-code-1009-request-for-future-version/610)

* * *

If you have additional questions that aren’t answered in those threads, feel free to ask.