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

Not all of the resources are cleared when destroying DurableExecutorService #14087

Closed
alparslanavci opened this issue Nov 8, 2018 · 3 comments

Comments

@alparslanavci
Copy link

commented Nov 8, 2018

When destroying a DurableExecutorService, the DurableExecutorPartitionContainer instances are not cleared. This makes some of the resources such as TaskRingBuffer still left in the heap even the service itself is destroyed.

@yilmazorhan

This comment has been minimized.

Copy link

commented Feb 27, 2019

Hello,
I was waiting for 3.12 for the fix. But it postponed for the next release.
Do you have a workaround for this issue?
Thanks

@galibey galibey self-assigned this Mar 26, 2019

mustafaiman added a commit to mustafaiman/hazelcast that referenced this issue Mar 26, 2019

Clears lefotver durable executor containers after destroy
DistributedDurableExecutorService did not clean containers removed via DurableExecutorService#destroy() call. This caused a leak.

fixes hazelcast#14087

@galibey galibey removed their assignment Mar 27, 2019

@mmedenjak mmedenjak modified the milestones: 3.13, 3.12 Mar 27, 2019

@mmedenjak

This comment has been minimized.

Copy link
Contributor

commented Mar 27, 2019

Hi @yilmazorhan ! The fix was just created in time for 3.12. We'll try and merge it.

mustafaiman added a commit that referenced this issue Mar 27, 2019

Clears lefotver durable executor containers after destroy
DistributedDurableExecutorService did not clean containers removed via DurableExecutorService#destroy() call. This caused a leak.

fixes #14087
@yilmazorhan

This comment has been minimized.

Copy link

commented Mar 29, 2019

Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.