246 — SnapshotUnavailable
transactionstorage
The read snapshot has expired and is no longer available
What is happening?
SnapshotTooOld is returned when a transaction or snapshot read attempts to access data at a point-in-time that WiredTiger has already purged. WiredTiger maintains a history of document versions for MVCC but regularly evicts old versions under cache pressure. Long-running transactions or reads at very old timestamps can encounter this when the required history is no longer available.
Common causes
- Transaction running too long while WiredTiger evicts old history
- WiredTiger cache pressure causing aggressive history eviction
- Reading with readConcern 'snapshot' at a timestamp older than available history
- Secondary read falling behind due to high replication lag