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 EBF76200CD7 for ; Tue, 1 Aug 2017 14:51:44 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id EA36A166F8F; Tue, 1 Aug 2017 12:51:44 +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 E1DC3166F7B for ; Tue, 1 Aug 2017 14:51:43 +0200 (CEST) Received: (qmail 5449 invoked by uid 500); 1 Aug 2017 12:51:42 -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 5438 invoked by uid 99); 1 Aug 2017 12:51:42 -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; Tue, 01 Aug 2017 12:51:42 +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 7CE6EC533F for ; Tue, 1 Aug 2017 12:51:42 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 3 X-Spam-Level: *** X-Spam-Status: No, score=3 tagged_above=-999 required=6.31 tests=[HTML_MESSAGE=2, KAM_LAZY_DOMAIN_SECURITY=1, RP_MATCHES_RCVD=-0.001, URIBL_BLOCKED=0.001] 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 CuIm9q7i4Uva for ; Tue, 1 Aug 2017 12:51:36 +0000 (UTC) Received: from mail.unitedplanet.com (mail.unitedplanet.com [213.164.80.197]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 52D365F485 for ; Tue, 1 Aug 2017 12:51:36 +0000 (UTC) Received: from Mailserver02.unitedplanet.de (unknown [10.10.12.102]) by mail.unitedplanet.com (Postfix) with ESMTP id 02F4819A935 for ; Tue, 1 Aug 2017 14:51:36 +0200 (CEST) Received: from Mailserver01.unitedplanet.de (10.10.12.100) by Mailserver02.unitedplanet.de (10.10.12.102) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.669.32; Tue, 1 Aug 2017 14:51:35 +0200 Received: from Mailserver01.unitedplanet.de ([fe80::e036:db95:f2ca:bb4d]) by Mailserver01.unitedplanet.de ([fe80::e036:db95:f2ca:bb4d%10]) with mapi id 15.01.0669.032; Tue, 1 Aug 2017 14:51:35 +0200 From: Juan Barani To: "'user@ignite.apache.org'" Subject: RE: Cache Groups and PARTITIONED/REPLICATED Thread-Topic: Cache Groups and PARTITIONED/REPLICATED Thread-Index: AdMKwMHE4XW+d7I6SDOZ7+UOTwEFtgAA8u0A Date: Tue, 1 Aug 2017 12:51:35 +0000 Message-ID: <3eaea2152f814a7da56572cf27d52448@unitedplanet.com> References: <6043bd3f00fa4a94b5681fe67aea3f48@unitedplanet.com> In-Reply-To: <6043bd3f00fa4a94b5681fe67aea3f48@unitedplanet.com> Accept-Language: en-US, de-DE Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.10.101.158] Content-Type: multipart/alternative; boundary="_000_3eaea2152f814a7da56572cf27d52448unitedplanetcom_" MIME-Version: 1.0 archived-at: Tue, 01 Aug 2017 12:51:45 -0000 --_000_3eaea2152f814a7da56572cf27d52448unitedplanetcom_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable I realized that if a have an global AtomicConfiguration like the following: final AtomicConfiguration atomicConfiguration =3D new AtomicConfiguration()= ; atomicConfiguration.setCacheMode(CacheMode.REPLICATED); igniteCfg.setAtomicConfiguration(atomicConfiguration); and I create a set with the default configuration, automatically the defaul= t config is partitioned, and the error appears. Then, it seems to be either I need to configure the CollectionConfiguration= exactly the same as the AtomicConfiguration, or place the Collection in a = different group altogether... Thanks, Juan From: Juan Barani Sent: Tuesday, August 1, 2017 2:22 PM To: user@ignite.apache.org Subject: Cache Groups and PARTITIONED/REPLICATED Hi! While trying the execute the very first snippet that creates a set in the d= ocumentation: https://apacheignite.readme.io/docs/queue-and-set#overview Ignite ignite =3D Ignition.ignite(); IgniteSet set =3D ignite.set( "setName", // Set name. null // Collection configuration. ); the returned set is always null. As soon as an empty configuration is passe= d, the set seems to work again. Is this the intended behavior? I guess eith= er the code or the documentation is outdated, can it be? Also, since updating from 2.0.0 to 2.1.0 we are getting the following error= message, apparently when sets are configured to be replicated and internal= caches (for atomics) are configured otherwise: class org.apache.ignite.IgniteException: Cache mode mismatch for caches rel= ated to the same group [groupName=3Ddefault-ds-group, existingCache=3Dignit= e-sys-atomic-cache@default-ds-group, existingCacheMode=3DPARTITIONED, start= ingCache=3Ddatastructures_ATOMIC_REPLICATED_0@default-ds-group, startingCac= heMode=3DREPLICATED] Should from 2.1.0 onwards caches/sets with different requirements be stored= in different cache groups? Thanks! Juan --_000_3eaea2152f814a7da56572cf27d52448unitedplanetcom_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

I realized that if a h= ave an global AtomicConfiguration like the following:

 

final AtomicConfigurat= ion atomicConfiguration =3D new AtomicConfiguration();

atomicConfiguration.se= tCacheMode(CacheMode.REPLICATED);

igniteCfg.setAtomicCon= figuration(atomicConfiguration);

 

and I create a set wit= h the default configuration, automatically the default config is partitione= d, and the error appears.

 

Then, it seems to be e= ither I need to configure the CollectionConfiguration exactly the same as t= he AtomicConfiguration, or place the Collection in a different group altoge= ther…

 

Thanks,


Juan

 

From: Juan Barani
Sent: Tuesday, August 1, 2017 2:22 PM
To: user@ignite.apache.org
Subject: Cache Groups and PARTITIONED/REPLICATED

 

Hi!

 

While trying the execute the very first snippet that= creates a set in the documentation:

 

https://apacheign= ite.readme.io/docs/queue-and-set#overview

 

Ignite ignite =3D <=
span class=3D"cm-variable">Ignition.i=
gnite();=

 
IgniteSetString> s=
et =3D ignite.set(=

    "setName"=
, // Set name.
    null   =
;    // C=
ollection configuration.<=
o:p>
);=

 

the returned set is always null. As soon as an empty= configuration is passed, the set seems to work again. Is this the intended= behavior? I guess either the code or the documentation is outdated, can it= be?

 

Also, since updating from 2.0.0 to 2.1.0 we are gett= ing the following error message, apparently when sets are configured to be = replicated and internal caches (for atomics) are configured otherwise:=

 

class org.apache.ignite.IgniteException: Cache mode = mismatch for caches related to the same group [groupName=3Ddefault-ds-group= , existingCache=3Dignite-sys-atomic-cache@default-ds-group, existingCacheMo= de=3DPARTITIONED, startingCache=3Ddatastructures_ATOMIC_REPLICATED_0@defaul= t-ds-group, startingCacheMode=3DREPLICATED]

 

Should from 2.1.0 onwards caches/sets with different= requirements be stored in different cache groups?

 

Thanks!

 

Juan

 

 

 

 

 

--_000_3eaea2152f814a7da56572cf27d52448unitedplanetcom_--