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

Gluu Server memory usage (3.1.0) #697

Closed
centroxy opened this Issue Aug 28, 2017 · 6 comments

Comments

Projects
None yet
5 participants
@centroxy

centroxy commented Aug 28, 2017

I am having an unusual behavior on Gluu server RC5
When I had installed Gluu server RC5. Free memory was 35%. After 3 days it was just 5% and Today, I had to restart the server as oxTrust did not work for me.

@yurem yurem added this to the CE 3.1.0 milestone Aug 28, 2017

@yurem yurem added the bug label Aug 28, 2017

@yurem yurem modified the milestones: CE 3.1.0, CE 3.1.1 Sep 7, 2017

@yurem

This comment has been minimized.

Contributor

yurem commented Sep 12, 2017

In CE default caching mode is "in_memory". If there is bug in this mode it can led to this issue.

@yuriyz

This comment has been minimized.

Contributor

yuriyz commented Sep 12, 2017

@centroxy would you please provide information how much memory is consumed by oxauth and how much by oxtrust(identity) ?

@yuriyz

This comment has been minimized.

Contributor

yuriyz commented Sep 12, 2017

@centroxy in addition, would you please set cache configuration to REDIS and check how it works. If we get memory issue with REDIS then it means that we have memory leaks and it is not related to cache.

@centroxy

This comment has been minimized.

centroxy commented Sep 12, 2017

Hi @yuriyz I am not sure how to reproduce this issue. On day 1 of the installation free Memory was 35% and after 5/6 days it slowly went down to 5 %. I will set the cache configuration and let you know. It may take a week to get back to you .

@nynymike

This comment has been minimized.

Contributor

nynymike commented Sep 12, 2017

Perhaps we can run a profiler for an extended period of time. It could be an uncleaned up collection or some other problem object.

@yurem yurem modified the milestones: CE 3.1.1, CE 3.1.2 Sep 26, 2017

@yurem

This comment has been minimized.

Contributor

yurem commented Oct 25, 2017

Final 3.1.1 version works stable on dev servers. We can move this issue to CE 3.1.3 when we will have more feedback about memory usage

@yurem yurem modified the milestones: CE 3.1.2, CE 3.2.0 Nov 7, 2017

@willow9886 willow9886 closed this Feb 20, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment