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

Under high load and high ICache.getAsync calls near-cache updates may cause OOM #8593

Closed
ihsandemir opened this issue Jul 25, 2016 · 1 comment

Comments

Projects
None yet
4 participants
@ihsandemir
Copy link
Contributor

commented Jul 25, 2016

Client updates ICache near cache using the ClientExecutionService userExecutor in an async way for getAsync API. The queue for the userExecutor is unbounded. If the userExecutor threads are slower in consuming these tasks in the executors queue, the queue may grow and this may cause OutOfMemory error. The queue items has reference to Invocation, Request ClientMessage and Response ClientMessage and these may be big objects.

@sancar

This comment has been minimized.

Copy link
Member

commented Dec 27, 2016

Fixed via #8649

@sancar sancar closed this Dec 27, 2016

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.