Pending put leaks when the entity is not found in DB

Description

When the entity is not found in DB, the registerForPendingPut is not followed by putFromLoad which should remove this pending put record. When the non-existing entry is not invalidated, the pending put can't be removed but by expiration - however, if these loads are executed more often than is the maxIdle timeout (by default 60s), the PendingPutMap grows beyond limits.

Activity

Show:

Former user August 12, 2015 at 9:07 PM

I've merged Radim's pull requests for 4.2 and 4.3. Thanks Radim!

Galder Zamarreno August 12, 2015 at 9:30 AM

Fixed in master, , are you backporting this to 4.2.x and 4.3.x?

Fixed

Details

Assignee

Reporter

Components

Fix versions

Priority

Created July 16, 2015 at 6:56 AM
Updated May 5, 2022 at 11:23 AM
Resolved May 5, 2022 at 11:23 AM