Context: In certain sections of our codebase, we invoke the logWriteConflictAndBackoff function to handle write conflicts. However, there are instances where we proceed with a backoff without releasing the snapshot, which may lead to resource locks or inefficient resource utilization. Example are here and here.
Objective: Ensure that whenever logWriteConflictAndBackoff is called, the snapshot is released before the backoff occurs. This will improve resource management and overall system efficiency.
- is related to
-
SERVER-88035 writeConflictRetry keeps snapshot open while backing off
-
- Closed
-