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

hazelcast objects destroy mechanism #7246

Closed
yangmin1989 opened this issue Jan 5, 2016 · 6 comments

Comments

Projects
None yet
3 participants
@yangmin1989
Copy link

commented Jan 5, 2016

I use Lock and Map via hazelcast.I find that the heap memory on hazelcast server keep increasing.All the Locks and Maps I created are destroyed by method destroy(),but the memory can not be destroyed by garbage collector even via FGC.So when my program run for some time,hazelcast server will go down.
Why?
I dumped the heap,and find that Locks and Maps has been destroyed.However, many other objects related to Locks and Maps are not been destroyed.So the more new Locks and Maps I create,the faster the heap increases.
There are the kind of object relavant still exist in heap when I destroy Lock and Map:
1.ConcurrentMap<ObjectNamespace, EntryTaskScheduler> evictionProcessors in LockServiceImpl
2.ConcurrentMap<ObjectNamespace, LockStoreImpl> lockStores in LockStoreContainer
3.ConcurrentMap<String, LocalMapStatsImpl> statsMap in LocalMapStatsProvider
Is this bugs of hazelcast? or hazelcast doesnt surpport the scene that keep creating new DistributedObjects and destroy them?
Attach files is the screenshot of the heap distribution.
expecting your answer,thanks

@yangmin1989

This comment has been minimized.

Copy link
Author

commented Jan 5, 2016

my hazelcast version is 3.4.1
Attach files is the screenshot of the heap distribution.

@pveentjer

This comment has been minimized.

Copy link
Member

commented Jan 5, 2016

Hi @yangmin1989 I saw your question on stackoverflow and since it contains very valuable information, I'll place it here:

http://stackoverflow.com/questions/34605244/hazelcast-objects-destroy-mechanism

Thank you for your excellent analysis.

Can you make a test that reproduces the issue?

@yangmin1989

This comment has been minimized.

Copy link
Author

commented Jan 5, 2016

@pveentjer I have reproduced the issue many times with the program which work for business of my company. if nessasary,i'd like to make a simple test for this issue and reproduce it once again.
thanks for your intention.

@yangmin1989

This comment has been minimized.

Copy link
Author

commented Jan 11, 2016

@pveentjer I write a simple project which can reproduce this issue. The code is here:
https://github.com/yangmin1989/hazelcast-test
Please review this issue.Thanks!

@yangmin1989

This comment has been minimized.

Copy link
Author

commented Jan 18, 2016

@pveentjer Have you reproduced this issue? I am expecting your response.Thanks!

@mdogan mdogan added this to the 3.8 milestone Nov 23, 2016

@mdogan

This comment has been minimized.

Copy link
Member

commented Jan 3, 2017

This issue is not reproducible since 3.6. Looks like already fixed. Following are related fixes:

#5673
#6951
#6971

@mdogan mdogan closed this Jan 3, 2017

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.