Return-Path: X-Original-To: apmail-ignite-user-archive@minotaur.apache.org Delivered-To: apmail-ignite-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 105F41917D for ; Fri, 29 Apr 2016 21:27:58 +0000 (UTC) Received: (qmail 38887 invoked by uid 500); 29 Apr 2016 21:27:57 -0000 Delivered-To: apmail-ignite-user-archive@ignite.apache.org Received: (qmail 38834 invoked by uid 500); 29 Apr 2016 21:27:57 -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 38824 invoked by uid 99); 29 Apr 2016 21:27:57 -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, 29 Apr 2016 21:27:57 +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 77810C8081 for ; Fri, 29 Apr 2016 21:27:57 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.173 X-Spam-Level: ** X-Spam-Status: No, score=2.173 tagged_above=-999 required=6.31 tests=[DKIM_ADSP_CUSTOM_MED=0.001, NML_ADSP_CUSTOM_MED=1.2, RCVD_IN_DNSWL_NONE=-0.0001, SPF_SOFTFAIL=0.972] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id Byho6Z1zzimF for ; Fri, 29 Apr 2016 21:27:55 +0000 (UTC) Received: from mbob.nabble.com (mbob.nabble.com [162.253.133.15]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 1353A5FAC9 for ; Fri, 29 Apr 2016 21:27:55 +0000 (UTC) Received: from malf.nabble.com (unknown [162.253.133.59]) by mbob.nabble.com (Postfix) with ESMTP id 84BA226755A5 for ; Fri, 29 Apr 2016 14:13:21 -0700 (PDT) Date: Fri, 29 Apr 2016 14:13:31 -0700 (PDT) From: vkulichenko To: user@ignite.apache.org Message-ID: <1461964411677-4709.post@n6.nabble.com> In-Reply-To: <1461960137588-4706.post@n6.nabble.com> References: <1461291932285-4437.post@n6.nabble.com> <1461345723061-4459.post@n6.nabble.com> <1461357317149-4469.post@n6.nabble.com> <1461624023744-4516.post@n6.nabble.com> <1461636393989-4524.post@n6.nabble.com> <1461782389374-4623.post@n6.nabble.com> <1461804036352-4636.post@n6.nabble.com> <1461845501128-4661.post@n6.nabble.com> <1461880410105-4675.post@n6.nabble.com> <1461960137588-4706.post@n6.nabble.com> Subject: Re: Client fails to connect - joinTimeout vs networkTimeout MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Caches always use affinity, it defines how the data is distributed across nodes. If you don't explicitly provide it in the configuration, RendezvousAffinityFunction will be used with excludeNeighbors=false. So if you want to enable this feature, you have to specify this in the configuration. -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Client-fails-to-connect-joinTimeout-vs-networkTimeout-tp4419p4709.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.