Hi, do you have query timeout configured? D.
On Thu, Aug 23, 2018 at 9:09 AM, dmitrievanthony <dmitrievanth...@gmail.com> wrote: > When I'm sending Scan Query request via Binary Client Protocol with very > big > page size I get OOM on the server node: > java.lang.OutOfMemoryError: Java heap space at > org.apache.ignite.internal.binary.streams.BinaryMemoryAllocatorChunk. > reallocate(BinaryMemoryAllocatorChunk.java:69) > at > org.apache.ignite.internal.binary.streams.BinaryHeapOutputStream. > ensureCapacity(BinaryHeapOutputStream.java:65) > at > org.apache.ignite.internal.binary.streams.BinaryAbstractOutputStream. > writeByteArray(BinaryAbstractOutputStream.java:41) > at > org.apache.ignite.internal.binary.BinaryWriterExImpl.doWriteByteArray( > BinaryWriterExImpl.java:530) > at > org.apache.ignite.internal.binary.BinaryClassDescriptor. > write(BinaryClassDescriptor.java:634) > at > org.apache.ignite.internal.binary.BinaryWriterExImpl. > marshal0(BinaryWriterExImpl.java:223) > at > org.apache.ignite.internal.binary.BinaryWriterExImpl. > marshal(BinaryWriterExImpl.java:164) > at > org.apache.ignite.internal.binary.BinaryWriterExImpl. > marshal(BinaryWriterExImpl.java:151) > at > org.apache.ignite.internal.binary.BinaryWriterExImpl.writeObjectDetached( > BinaryWriterExImpl.java:1506) > at > org.apache.ignite.internal.processors.platform.client.cache. > ClientCacheEntryQueryCursor.writeEntry(ClientCacheEntryQueryCursor. > java:44) > at > org.apache.ignite.internal.processors.platform.client.cache. > ClientCacheEntryQueryCursor.writeEntry(ClientCacheEntryQueryCursor. > java:29) > at > org.apache.ignite.internal.processors.platform.client. > cache.ClientCacheQueryCursor.writePage(ClientCacheQueryCursor.java:80) > at > org.apache.ignite.internal.processors.platform.client.cache. > ClientCacheQueryResponse.encode(ClientCacheQueryResponse.java:50) > at > org.apache.ignite.internal.processors.platform.client. > ClientMessageParser.encode(ClientMessageParser.java:379) > at > org.apache.ignite.internal.processors.odbc.ClientListenerNioListener. > onMessage(ClientListenerNioListener.java:172) > at > org.apache.ignite.internal.processors.odbc.ClientListenerNioListener. > onMessage(ClientListenerNioListener.java:45) > at > org.apache.ignite.internal.util.nio.GridNioFilterChain$ > TailFilter.onMessageReceived(GridNioFilterChain.java:279) > at > org.apache.ignite.internal.util.nio.GridNioFilterAdapter. > proceedMessageReceived(GridNioFilterAdapter.java:109) > at > org.apache.ignite.internal.util.nio.GridNioAsyncNotifyFilter$3. > body(GridNioAsyncNotifyFilter.java:97) > at > org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110) > at > org.apache.ignite.internal.util.worker.GridWorkerPool$1. > run(GridWorkerPool.java:70) > at > java.util.concurrent.ThreadPoolExecutor.runWorker( > ThreadPoolExecutor.java:1149) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run( > ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:748)Exception in thread > "client-connector-#61" java.lang.OutOfMemoryError: Java heap space at > org.apache.ignite.internal.binary.streams.BinaryMemoryAllocatorChunk. > reallocate(BinaryMemoryAllocatorChunk.java:69) > at > org.apache.ignite.internal.binary.streams.BinaryHeapOutputStream. > ensureCapacity(BinaryHeapOutputStream.java:65) > at > org.apache.ignite.internal.binary.streams.BinaryAbstractOutputStream. > writeByteArray(BinaryAbstractOutputStream.java:41) > at > org.apache.ignite.internal.binary.BinaryWriterExImpl.doWriteByteArray( > BinaryWriterExImpl.java:530) > at > org.apache.ignite.internal.binary.BinaryClassDescriptor. > write(BinaryClassDescriptor.java:634) > at > org.apache.ignite.internal.binary.BinaryWriterExImpl. > marshal0(BinaryWriterExImpl.java:223) > at > org.apache.ignite.internal.binary.BinaryWriterExImpl. > marshal(BinaryWriterExImpl.java:164) > at > org.apache.ignite.internal.binary.BinaryWriterExImpl. > marshal(BinaryWriterExImpl.java:151) > at > org.apache.ignite.internal.binary.BinaryWriterExImpl.writeObjectDetached( > BinaryWriterExImpl.java:1506) > at > org.apache.ignite.internal.processors.platform.client.cache. > ClientCacheEntryQueryCursor.writeEntry(ClientCacheEntryQueryCursor. > java:44) > at > org.apache.ignite.internal.processors.platform.client.cache. > ClientCacheEntryQueryCursor.writeEntry(ClientCacheEntryQueryCursor. > java:29) > at > org.apache.ignite.internal.processors.platform.client. > cache.ClientCacheQueryCursor.writePage(ClientCacheQueryCursor.java:80) > at > org.apache.ignite.internal.processors.platform.client.cache. > ClientCacheQueryResponse.encode(ClientCacheQueryResponse.java:50) > at > org.apache.ignite.internal.processors.platform.client. > ClientMessageParser.encode(ClientMessageParser.java:379) > at > org.apache.ignite.internal.processors.odbc.ClientListenerNioListener. > onMessage(ClientListenerNioListener.java:172) > at > org.apache.ignite.internal.processors.odbc.ClientListenerNioListener. > onMessage(ClientListenerNioListener.java:45) > at > org.apache.ignite.internal.util.nio.GridNioFilterChain$ > TailFilter.onMessageReceived(GridNioFilterChain.java:279) > at > org.apache.ignite.internal.util.nio.GridNioFilterAdapter. > proceedMessageReceived(GridNioFilterAdapter.java:109) > at > org.apache.ignite.internal.util.nio.GridNioAsyncNotifyFilter$3. > body(GridNioAsyncNotifyFilter.java:97) > at > org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110) > at > org.apache.ignite.internal.util.worker.GridWorkerPool$1. > run(GridWorkerPool.java:70) > at > java.util.concurrent.ThreadPoolExecutor.runWorker( > ThreadPoolExecutor.java:1149) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run( > ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:748) > And it's understandable. But at the same time, the connection doesn't > interrupts and my client hangs on recv call until I manually kill Ignite > server node. Is it a knows issue? > > > > -- > Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
