Details
-
Bug
-
Resolution: Fixed
-
Major - P3
-
None
-
None
-
None
-
Fully Compatible
-
ALL
-
Execution Team 2019-12-16, Execution Team 2019-12-30
-
20
Description
There are a few places in OplogBatcher::_run that access the storage engine, like getBatchLimitOplogBytes(), which reads from the DurableCatalog.
WT may occasionally return WT_ROLLBACK for reads when the cache is full, so this internal thread needs to be able to handle the possibility of a WriteConflictException without it escaping.