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

Heap space issue : net.spy.memcached.protocol.binary.BinaryMemcachedNodeImpl #410

Open
shobero opened this issue Aug 29, 2019 · 2 comments

Comments

@shobero
Copy link

shobero commented Aug 29, 2019

We are using memcache for session storage but on few nodes which are not restarted for more than a week it has been noticed that net.spy.memcached.protocol.binary.BinaryMemcachedNodeImpl class has occupied close to or more than 50% of total heap memory and not getting cleared even after major GC run.

Attaching heap memory snapshot for reference.
Note : Nodes with this issue has writeQ (java.util.concurrent.LinkedBlockingQueue) size more than 400K (looks like cyclic dependency) where as other nodes which are working fine has writeQ size of 0.

Screen Shot 2019-08-29 at 6 10 52 PM

Detailed snapshot of writeQ
Screen Shot 2019-08-29 at 6 10 37 PM

Can someone help me in figuring out what is the cause of this issue?

@mako-fdc
Copy link

@shobero If you use memcached as a backend, this problem might be related to couchbase/spymemcached#38

You might want to check to your tomcat logs for errors, i.e. the catalina.out.

@pjain1
Copy link

pjain1 commented Aug 4, 2021

We have seen this issue in our cluster as well and this queue which is the operation queue was occupying almost 90% of the heap, I think this happens because of high concurrent load. A workaround is to limit the queue size by implementing custom operation queue like here and using that in the ConnectionFactory. Note - I did not implement any of it, just using it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants