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 A8331200CCA for ; Wed, 19 Jul 2017 23:30:59 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id A68D8169DF2; Wed, 19 Jul 2017 21:30:59 +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 ED272169DF0 for ; Wed, 19 Jul 2017 23:30:58 +0200 (CEST) Received: (qmail 44739 invoked by uid 500); 19 Jul 2017 21:30:53 -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 44728 invoked by uid 99); 19 Jul 2017 21:30:53 -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; Wed, 19 Jul 2017 21:30:53 +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 9C88DC2FB8 for ; Wed, 19 Jul 2017 21:30:52 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.174 X-Spam-Level: ** X-Spam-Status: No, score=2.174 tagged_above=-999 required=6.31 tests=[DKIM_ADSP_CUSTOM_MED=0.001, NML_ADSP_CUSTOM_MED=1.2, SPF_SOFTFAIL=0.972, URIBL_BLOCKED=0.001] 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 d_saBcSbgNw5 for ; Wed, 19 Jul 2017 21:30:44 +0000 (UTC) Received: from mwork.nabble.com (mwork.nabble.com [162.253.133.43]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 622325F6D3 for ; Wed, 19 Jul 2017 21:30:44 +0000 (UTC) Received: from static.162.255.23.37.macminivault.com (unknown [162.255.23.37]) by mwork.nabble.com (Postfix) with ESMTP id 26F805457666F for ; Wed, 19 Jul 2017 14:30:44 -0700 (MST) Date: Wed, 19 Jul 2017 14:30:44 -0700 (MST) From: vkulichenko To: user@ignite.apache.org Message-ID: <1500499844152-15143.post@n6.nabble.com> In-Reply-To: <1500494157939-15138.post@n6.nabble.com> References: <1500494157939-15138.post@n6.nabble.com> Subject: Re: Large value of idleConnectionTimeout in TcpCommunicationSpi MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit archived-at: Wed, 19 Jul 2017 21:30:59 -0000 Amit, Default idle timeout is actually 10 minutes. Therefore connection will be closed only it is not used for at least 10 minutes, not 30 seconds. Are you sure that delay is caused by reopening a closed connection? If yes, are you sure it's caused by idle timeout? Answering your questions: 1. Generally it's OK, but I recommend you to investigate more first. What you tell doesn't sound right. 2. The only drawback is that you spend resources on a connection that is not used. In most cases this is not an issue. 3. If one of the parties shuts down, connection is closed anyway. 4. On all nodes. -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Large-value-of-idleConnectionTimeout-in-TcpCommunicationSpi-tp15138p15143.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.