From dev-return-38189-archive-asf-public=cust-asf.ponee.io@ignite.apache.org Thu Aug 23 19:33:10 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id B39D718061A for ; Thu, 23 Aug 2018 19:33:09 +0200 (CEST) Received: (qmail 77999 invoked by uid 500); 23 Aug 2018 17:33:08 -0000 Mailing-List: contact dev-help@ignite.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ignite.apache.org Delivered-To: mailing list dev@ignite.apache.org Received: (qmail 77988 invoked by uid 99); 23 Aug 2018 17:33:08 -0000 Received: from mail-relay.apache.org (HELO mailrelay1-lw-us.apache.org) (207.244.88.152) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 23 Aug 2018 17:33:08 +0000 Received: from mail-oi0-f54.google.com (mail-oi0-f54.google.com [209.85.218.54]) by mailrelay1-lw-us.apache.org (ASF Mail Server at mailrelay1-lw-us.apache.org) with ESMTPSA id A64E34EF2 for ; Thu, 23 Aug 2018 17:33:07 +0000 (UTC) Received: by mail-oi0-f54.google.com with SMTP id q11-v6so10615637oic.12 for ; Thu, 23 Aug 2018 10:33:07 -0700 (PDT) X-Gm-Message-State: APzg51AEJXRj6kJ9miolHDeJHk3WPIueOSJGFPryoBv2DuJqxHa9rQdk 2hR7ysIFL/X5KQzP2l6xTQyDZecqX3ITo17wM4HL9A== X-Google-Smtp-Source: ANB0VdYqM6b5qvBDVvks9dYhGUwI880lLeGbJASp/JLjJfb9AK80vdGKNfv/m8xbv1vpOQYBDnxLpVAxiNR0RsaKOho= X-Received: by 2002:aca:4141:: with SMTP id o62-v6mr9911854oia.24.1535045587100; Thu, 23 Aug 2018 10:33:07 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:ac9:3344:0:0:0:0:0 with HTTP; Thu, 23 Aug 2018 10:32:26 -0700 (PDT) In-Reply-To: <1535040561863-0.post@n4.nabble.com> References: <1535040561863-0.post@n4.nabble.com> From: Dmitriy Setrakyan Date: Thu, 23 Aug 2018 10:32:26 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Binary Client Protocol client hangs in case of OOM on server To: dev Content-Type: multipart/alternative; boundary="000000000000eeff2d05741da633" --000000000000eeff2d05741da633 Content-Type: text/plain; charset="UTF-8" Hi, do you have query timeout configured? D. On Thu, Aug 23, 2018 at 9:09 AM, dmitrievanthony 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/ --000000000000eeff2d05741da633--