Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id A5445200D60 for ; Fri, 1 Dec 2017 10:28:35 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id A391F160C06; Fri, 1 Dec 2017 09:28:35 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id E5DC4160BFB for ; Fri, 1 Dec 2017 10:28:34 +0100 (CET) Received: (qmail 7331 invoked by uid 500); 1 Dec 2017 09:28:33 -0000 Mailing-List: contact user-help@ignite.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@ignite.apache.org Delivered-To: mailing list user@ignite.apache.org Received: (qmail 7321 invoked by uid 99); 1 Dec 2017 09:28:33 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 01 Dec 2017 09:28:33 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 15384C252F for ; Fri, 1 Dec 2017 09:28:33 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.372 X-Spam-Level: ** X-Spam-Status: No, score=2.372 tagged_above=-999 required=6.31 tests=[DKIM_ADSP_CUSTOM_MED=0.001, KB_WAM_FROM_NAME_SINGLEWORD=0.2, NML_ADSP_CUSTOM_MED=1.2, SPF_HELO_PASS=-0.001, SPF_SOFTFAIL=0.972] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id thXxsYbJLkdK for ; Fri, 1 Dec 2017 09:28:32 +0000 (UTC) Received: from n6.nabble.com (n6.nabble.com [162.255.23.37]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 0D5DB5F46D for ; Fri, 1 Dec 2017 09:28:32 +0000 (UTC) Received: from n6.nabble.com (localhost [127.0.0.1]) by n6.nabble.com (Postfix) with ESMTP id 7EC4E3325430 for ; Fri, 1 Dec 2017 02:28:31 -0700 (MST) Date: Fri, 1 Dec 2017 02:28:31 -0700 (MST) From: "ilya.kasnacheev" To: user@ignite.apache.org Message-ID: <1512120511515-0.post@n6.nabble.com> In-Reply-To: References: Subject: Re: Socket Reader Timeout on ClientImpl MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit archived-at: Fri, 01 Dec 2017 09:28:35 -0000 Hello Tolga! First of all, Ignite has two kinds of connections: Discovery connections and Communication connections. Discovery connections form a ring and make sure node requires topology updates, Communication connections established between nodes and are used to pass data. ClientImpl should not be your concern here, as it reads from Discovery socket and it's normal mode of operation to wait on socket. What should concern you is Communication timeouts, you can set socketWriteTimeout and connectTimeout on TcpCommunicationSpi in Ignite configuration. However in your case it's likely that hang is not related to network problems. Please consider logs of your nodes - any thread pool starvation messages? Exceptions? Failures to wait for exchanges? In your case there's likely to be the latter: - parking to wait for <0x00000007d9608000> (a org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture) Some node is unable to finish exchange due to long running transactions or other problems, please scoop logs carefully for errors, post the most interesting findings here. The exchange in question was likely initiated by attempting to start a new cache, as apparent by: - parking to wait for <0x00000007d964b7a8> (a org.apache.ignite.internal.processors.cache.GridCacheProcessor$DynamicCacheStartFuture) Regards, -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/