From user-return-25831-apmail-ignite-user-archive=ignite.apache.org@ignite.apache.org Fri May 3 08:36:22 2019 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 [207.244.88.153]) by minotaur.apache.org (Postfix) with SMTP id CA2B0199B4 for ; Fri, 3 May 2019 08:36:21 +0000 (UTC) Received: (qmail 61251 invoked by uid 500); 3 May 2019 08:36:17 -0000 Delivered-To: apmail-ignite-user-archive@ignite.apache.org Received: (qmail 61215 invoked by uid 500); 3 May 2019 08:36:17 -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 61193 invoked by uid 99); 3 May 2019 08:36:16 -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; Fri, 03 May 2019 08:36:16 +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 497EA180D6C for ; Fri, 3 May 2019 08:36:16 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.8 X-Spam-Level: * X-Spam-Status: No, score=1.8 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Authentication-Results: spamd3-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-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 0EvZm2JNgQyN for ; Fri, 3 May 2019 08:36:14 +0000 (UTC) Received: from mail-io1-f46.google.com (mail-io1-f46.google.com [209.85.166.46]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id B18B75F232 for ; Fri, 3 May 2019 08:36:13 +0000 (UTC) Received: by mail-io1-f46.google.com with SMTP id c24so4477888iom.9 for ; Fri, 03 May 2019 01:36:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=TNFPgPKrg9m4OabbjwQdIX7tOASAy7gXFSTRDz7yqg8=; b=Df1qmYYbyoM5DNDctBnx7MxWT4bUaoZs/APUtyAPFXskq+jozT0qe54cNXFUS6FmtJ pZnYRenXXN2+GV+B99ZnrAePjidveM2SlpRzmnNfmUECQ0IvIqWL+K9fixmarJaz87RG ZF6Xawz9HWxSbMpuTqpYLVZudaJJslPloo4YpaMLBIJ7H4gGP6jjLRS1v6dJfPbMSbV8 Ys9BgEy/OAiZiUcjAGOV7w7M5nkh3/hxghAzhGkyFYeum++9ALu2dMg4YwS4evGEFTt6 zefhk1YxoRf/TBNodo6sj49AFA5bp2BGv2CwLt5PfE9CILECHIf+QUFT8OQ1KMWMCp4P we/w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=TNFPgPKrg9m4OabbjwQdIX7tOASAy7gXFSTRDz7yqg8=; b=FxYAGd+wBuDb0qCyra8/Nvj/Ts7syaIglwtr/M6Vet1KFDXnCs85w0rG3Rfcgh6Ypr qxrkYjTWhfOf45Egmr+/mhYOKCo+OQRY8LdM/cQANQG6PqB6IClPFwgzLsONyihUMPwq u+eGipYq0oh8O9S/uBBPWro+P5MM4ZNWwTAv3JkPDp+pY8j9JXJnki6LgmK3dtUE1a3Y d/34TwrV8F/G/ShHYmTIyVqHSwfKPwAWvp8NmZlteLOjuecXfUxNvXZ7r3iqROoqPb6h b480/42rQAMnnCGgn9XjwK1wWRBkZkF/j7H58KtAZ/Ia0PMcfFCdq9DZayIsAmsQfRK/ 5c1A== X-Gm-Message-State: APjAAAUwfGCY4zk1iOUEyFr72BhTvtqHFMt392E8KKsjtdU6kSutEaT2 Yb/Wcm9GZLJ3/N/VXVy7RZ8R69Vr2x0VKrvaf97/fWtf X-Google-Smtp-Source: APXvYqxpoyeCWIN4zUB8vvCNpf0lZAWUBPSqEgGl2C6laQQAhZUmJb70MYu0CLCWj64QC0dO3qeIE9i2AWevkC2TJkg= X-Received: by 2002:a6b:b50b:: with SMTP id e11mr5128007iof.144.1556872572338; Fri, 03 May 2019 01:36:12 -0700 (PDT) MIME-Version: 1.0 References: <1556794901262-0.post@n6.nabble.com> <1556861234482-0.post@n6.nabble.com> In-Reply-To: <1556861234482-0.post@n6.nabble.com> From: Evgenii Zhuravlev Date: Fri, 3 May 2019 11:35:59 +0300 Message-ID: Subject: Re: How data region is propagated to other nodes To: user@ignite.apache.org Content-Type: multipart/alternative; boundary="000000000000a287d50587f7a4e5" --000000000000a287d50587f7a4e5 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Then you can simply create 2 different data regions for all server nodes in the cluster - one with persistence and one without. After that, you can decide, how you want to store your key - with persistence or without. Evgenii =D0=BF=D1=82, 3 =D0=BC=D0=B0=D1=8F 2019 =D0=B3. =D0=B2 08:27, dhiman_nikhil= : > As per documentation, I can do persistence in data region only. If I > wanted a > cache key to be persisted then I have to make sure that data region to be > replicated across all nodes. > > Basically, my requirement is to give multi-tenancy support[Multiple > Applications can communicate to Ignite Cluster]. To prevent conflict of > CacheKey, I will be writing an Ignite Client[Wrapper over IgniteClient > library] and passing on the limiting functionality to Services[Like they > can > get CacheKey, but not been able to create it]. > > If a new Application comes and demands a CacheKey with persistence ON, we > should be able to provide it without reloading the whole nodes of Ignite > cluster. > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ > --000000000000a287d50587f7a4e5 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Then you can simply create 2 different data regions for al= l server nodes in the cluster - one with persistence and one without. After= that, you can decide, how you want to store your key - with persistence or= without.

Evgenii

=D0=BF=D1=82, 3 =D0=BC=D0=B0=D1= =8F 2019 =D0=B3. =D0=B2 08:27, dhiman_nikhil <nikcomestotalk@gmail.com>:
As per documentation, I can do persistence in data region only. If I wan= ted a
cache key to be persisted then I have to make sure that data region to be replicated across all nodes.

Basically, my requirement is to give multi-tenancy support[Multiple
Applications can communicate to Ignite Cluster]. To prevent conflict of
CacheKey, I will be writing an Ignite Client[Wrapper over IgniteClient
library] and passing on the limiting functionality to Services[Like they ca= n
get CacheKey, but not been able to create it].

If a new Application comes and demands a CacheKey with persistence ON, we should be able to provide it without reloading the whole nodes of Ignite cluster.



--
Sent from: http://apache-ignite-users.70518.x6.nabbl= e.com/
--000000000000a287d50587f7a4e5--