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

Memory consumption in com.hazelcast.impl.base.SystemLogService #325

Closed
alexturc opened this issue Oct 21, 2012 · 7 comments

Comments

Projects
None yet
7 participants
@alexturc
Copy link

commented Oct 21, 2012

I have a one node hazelcast cluster. Ran for about two days and ended up having 25% of used memory (165MB in total) bound to com.hazelcast.impl.base.SystemLogService. To be more specific, it seems that SysmteLogService.joinLogs queue is holding on to some data.

https://github.com/alexturc/github-attachments/blob/master/Hazelcast-SystemLogService-MemoryUsage-1.png?raw=true

https://github.com/alexturc/github-attachments/blob/master/Hazelcast-SystemLogService-MemoryUsage-2.png?raw=true

@pagrus7

This comment has been minimized.

Copy link

commented Nov 15, 2012

I'm having a similar issue, although in my case it is SystemLogService.mapCallStates that grows.
https://groups.google.com/forum/#!topic/hazelcast/1JSgF7pc7tw

@gnilron

This comment has been minimized.

Copy link

commented Apr 10, 2013

Any news on this issue? We see similar issues with Hazelcast 2.3.1. Would upgrading to 2.5 make any difference regarding this?

@enesakar

This comment has been minimized.

Copy link
Member

commented Apr 10, 2013

You can disable system logs by setting property "hazelcast.system.log.enabled" to false. (starting from version 2.4.1)

@MrEasy

This comment has been minimized.

Copy link
Contributor

commented Jun 3, 2013

Also stumbled across this one. Problem are the states, which are added to Map "mapCallStates" and never released. To demonstrate how severe this can become, have a look at the following screenshots. IMHO if not fixedm then at least the default of "hazelcast.system.log.enabled" should be set to false.

leak

systemlogservice

@pveentjer

This comment has been minimized.

Copy link
Member

commented Jun 27, 2013

Which version of HZ are you using?

And can you provide an example that reproduces the problem. This makes it a lot easier for us to debug and solve the actual issue.

PS:
I see that the xxxLogs queues and the mapCallStates ConcurrentMap are not cleaned; so once stuf it added it will remain added.

@pveentjer

This comment has been minimized.

Copy link
Member

commented Jun 27, 2013

I have created a pr that fixed this for 2.x branch and I'll do a cherry pick once that request has been merged for the 3.x branch.

And as Enes mentioned, by disabling the SystemLogService with the "hazelcast.system.log.enabled" property, no log entries are stored at all.

@ghost ghost assigned pveentjer Jun 29, 2013

@mdogan

This comment has been minimized.

Copy link
Member

commented Jun 29, 2013

Closed by pull request #524

@mdogan mdogan closed this Jun 29, 2013

ispringer pushed a commit to ghinkle/hazelcast that referenced this issue Oct 30, 2013

* fix #hazelcast#325
* some minor improvements for object creation prevent if no logging needed
* some minor code cleanup (extract constant)

ispringer pushed a commit to ghinkle/hazelcast that referenced this issue Oct 30, 2013

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.