You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
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