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 77F20200AF8 for ; Thu, 5 May 2016 16:27:53 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 75B4F160A03; Thu, 5 May 2016 14:27:53 +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 BF9621609F3 for ; Thu, 5 May 2016 16:27:52 +0200 (CEST) Received: (qmail 56438 invoked by uid 500); 5 May 2016 14:27:51 -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 56428 invoked by uid 99); 5 May 2016 14:27:51 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 May 2016 14:27:51 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 884BB180184 for ; Thu, 5 May 2016 14:27:51 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-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 mx2-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id yid1ORBbx93n for ; Thu, 5 May 2016 14:27:49 +0000 (UTC) Received: from mbob.nabble.com (mbob.nabble.com [162.253.133.15]) by mx2-lw-eu.apache.org (ASF Mail Server at mx2-lw-eu.apache.org) with ESMTP id 71C3F60D2C for ; Thu, 5 May 2016 14:27:49 +0000 (UTC) Received: from malf.nabble.com (unknown [162.253.133.59]) by mbob.nabble.com (Postfix) with ESMTP id E017D26E5EE0 for ; Thu, 5 May 2016 07:12:38 -0700 (PDT) Date: Thu, 5 May 2016 07:13:14 -0700 (PDT) From: zshamrock To: user@ignite.apache.org Message-ID: <1462457594775-4792.post@n6.nabble.com> In-Reply-To: References: <1462372647999-4768.post@n6.nabble.com> Subject: Re: Ignite client near cache conflicts with server distributed cache MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit archived-at: Thu, 05 May 2016 14:27:53 -0000 Yes, removing definition of the cache from IgniteConfiguration, helps. And I know about this. The point was that I wanted for the client to be self sufficient, i.e. to create all the distributed server caches first (by providing cache definition for IgniteConfiguration), and then configure the near cache. Although, I've switched from this direction, and only configure now near cache for the client. But, still the scenario described could be a valid one. And it is for you to evaluate whether this is the expected behavior or a bug. Thank you. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Ignite-client-near-cache-conflicts-with-server-distributed-cache-tp4768p4792.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.