Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix(Memory Leak): Remove FencedLockProxy upon FencedLock#destroy [HZ-3039] [5.3.z] #25421

Merged
merged 1 commit into from
Sep 12, 2023

Conversation

gbarnett-hz
Copy link
Contributor

Removes the FencedLockProxy from LockService.proxies after calling legacy semantics of AbstractBlockingService#destroyRaftObject. Previously the FencedLockProxy would be resident in LockService.proxies until the CP system was reset.

Fixes #25344

Backport of: #25353

…3039] (hazelcast#25353)

Removes the `FencedLockProxy` from `LockService.proxies` _after_ calling
legacy semantics of `AbstractBlockingService#destroyRaftObject`.
Previously the `FencedLockProxy` would be resident in
`LockService.proxies` until the CP system was reset.

Fixes hazelcast#25344

(cherry picked from commit e301940)
@gbarnett-hz gbarnett-hz self-assigned this Sep 12, 2023
@arodionov arodionov changed the title Fix(Memory Leak): Remove FencedLockProxy upon FencedLock#destroy [HZ-3039] Fix(Memory Leak): Remove FencedLockProxy upon FencedLock#destroy [HZ-3039] [5.3.z] Sep 12, 2023
@arodionov arodionov added this to the 5.3.z milestone Sep 12, 2023
@degerhz degerhz modified the milestones: 5.3.z, 5.3.3 Sep 12, 2023
@gbarnett-hz gbarnett-hz merged commit d82c8f3 into hazelcast:5.3.z Sep 12, 2023
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants