Error
Error Code: 136

MongoDB Error 136: Capped Cursor Position Lost

📦 MongoDB
📋

Description

This error indicates that a tailable cursor has lost its position within a capped collection. This typically occurs when the cursor attempts to read a document that has already been overwritten or removed due to the capped collection's fixed size and FIFO (First-In, First-Out) behavior.
💬

Error Message

Capped Position Lost
🔍

Known Causes

3 known causes
⚠️
Data Overwritten
New documents have been inserted into the capped collection, pushing the document the cursor was tracking out of the collection's fixed size.
⚠️
Collection Rollover
The entire capped collection has been filled and wrapped around, meaning all original data, including the cursor's position, has been overwritten.
⚠️
Inactive Tailable Cursor
A tailable cursor remained idle for too long, allowing subsequent writes to overwrite the data it was attempting to read next.
🛠️

Solutions

Coming Soon

Detailed step-by-step solutions for this error are being prepared. In the meantime, try these general troubleshooting tips:

General Troubleshooting Tips

  • Check the error message carefully for specific details
  • Review recent changes that might have caused the error
  • Search for the exact error code in the official documentation
  • Check log files for additional context
  • Try restarting the application or service
🔗

Related Errors

5 related errors