fetchRingBufferSize should be global to all the created RingBufferThread in a JVM #48
Unanswered
odelpozo-denodo
asked this question in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hello
Some Denodo Technologies customers are facing java.lang.OutOfMemoryError issues executing Redshift queries in a concurrent way with the Reshift 2.x JDBC drivers. By default, the enableFetchRingBuffer feature is enabled and multiple instances of RingBufferThread are created with 1GB of max size when multiple queries are executed.
When this happens, as the buffers are filling up, the heap memory grows and, eventually, a java.lang.OutOfMemoryError is raised:
I think that the fetchRingBufferSize should limit the total JVM memory used by all the RingBufferThread instances, not the size of each RingBufferThread instance. Otherwise, JDBC clients with concurrent queries should not enable the RingBuffer feature to avoid possible OOM issues.
Beta Was this translation helpful? Give feedback.
All reactions