The update resolution as part of commit/rollback does the fast path or a slow path:

• Fast path: Successfully upgrades a weak hazard pointer to a strong pointer. Holding the pointer till the update is resolved, releasing there after.
• Slow path: On failing the weak pointer upgrade, use a cursor to search for the update. Keeps the cursor positioned (and hence a strong pointer taken) till the update is resolved. Then proceeds to resolve another update, which results in releasing the strong pointer on the former update.

In both cases, since the strong pointer is released when we start to process the next update, there is nothing preventing the already processed updates from being evicted.

This ticket will focus on designing and making changes for an approach to resolve this issue.