Until SERVER-81493, MongoDB made an assumption that WT_CURSOR::reset() would never return WT_ROLLBACK. That still appears to be true, but it's not well-defined in the API. We would like the WT API to explicitly tell us whether or not that is possible.
We would prefer that reset() cannot throw WT_ROLLBACK, because we often reset cursors in destructors. Since we convert WT_ROLLBACK to WriteConflictExceptions, we risk crashing, since exceptions cannot be thrown in destructors.
- is related to
-
WT-13257 Make sure that eviction side activity is transparent to the user
-
- Closed
-
-
SERVER-91890 plan executor impl doesn't retry storage unavailable exceptions on calls to save state
-
- Closed
-
-
WT-13306 Investigate ways to reduce the set of errors returned by cursor->reset()
-
- Open
-
- related to
-
-
- Closed
-
-
-
- Closed
-
-
WT-13304 Clarify WT_ROLLBACK in documentation
-
- Open
-