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 B93C5200B9B for ; Wed, 12 Oct 2016 08:59:25 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id B7EB5160AD3; Wed, 12 Oct 2016 06:59:25 +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 AB874160AD4 for ; Wed, 12 Oct 2016 08:59:24 +0200 (CEST) Received: (qmail 21452 invoked by uid 500); 12 Oct 2016 06:59:23 -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 21338 invoked by uid 99); 12 Oct 2016 06:59:23 -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; Wed, 12 Oct 2016 06:59:23 +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 555721806F7 for ; Wed, 12 Oct 2016 06:59:23 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.179 X-Spam-Level: * X-Spam-Status: No, score=1.179 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-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-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id eLDPJ9PHK_hW for ; Wed, 12 Oct 2016 06:59:20 +0000 (UTC) Received: from mail-yb0-f174.google.com (mail-yb0-f174.google.com [209.85.213.174]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id 24CF15F201 for ; Wed, 12 Oct 2016 06:59:20 +0000 (UTC) Received: by mail-yb0-f174.google.com with SMTP id e20so16747051ybb.0 for ; Tue, 11 Oct 2016 23:59:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=ILn43ST+/wdEBiQXVjsvhWYCBUl/Q8nLvIrMcXe9nB4=; b=GrUh3ZInfSsILo95wgCUc98cEAaN+SmPsCWsT7lXA40WkzCP/Quym78eA3PHeq5aev 3lXzJ4xZlWujzzmgpkE6Pglh612xUrx4Qx3tfYW8G2gssnThXO8Y+vANaUrd0tW9Fm8T pOYxoa3Fo/ufMFyLsSUdOmtYMX4F82MvxU7XPJB7+ze1Y5tkX1LN+RpnxgnQKDHLdk3p FyfFBBohH/Kn/C3lnu9g66lw5SKfU+v7p+8UtWgxHoPvYXDhKUmY3UjdOdm7ACLxyOdk UAc0GxzpdUB9ehqAC6JYdvNxy+9Gy6/lGxYpc/SiXC6xz1l6ckmuiwhvAIgr5KDPiyn/ BS/w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=ILn43ST+/wdEBiQXVjsvhWYCBUl/Q8nLvIrMcXe9nB4=; b=EPantHZkgP1iHf76xvG0+mRh38HGGLHCm2iSDlrjDy29k8y3xTwGxNTTK+L4f/t09J MfD07/goE4NC5OyTzqsZUMZSRwoRqDM/SI0y6yZugPlXduZuhq68YNyG3Oyc+pitAFGu cydFRBURHmngVAM0tQrI1OACE1QQg029FDnMwogihgdLYx6P2EGTy2rBGvT9HIwdJM7O lbnHzj9FHjGEJkUjgreCUYamAtiyv/z8etNZl+L2VlX/DqzHD7diH2RTE3hq0NreQlwV nWmS6LOsL/uI5f/VBF1XBLdwtLAIpzOP+GK8CUPGqpMdNFkxghVHO9wONkHoqj0rHxTr JUmg== X-Gm-Message-State: AA6/9RmE2CB9FLFP5wG3CAGyt5VJkBZV+IhZbzweQKKcrsoJ1eD/0pUlMzSO3D90OmVGnN7QmuMBheKAH5OOew== X-Received: by 10.37.207.194 with SMTP id f185mr6841694ybg.33.1476255555358; Tue, 11 Oct 2016 23:59:15 -0700 (PDT) MIME-Version: 1.0 Received: by 10.37.223.213 with HTTP; Tue, 11 Oct 2016 23:59:14 -0700 (PDT) In-Reply-To: References: From: Vladislav Pyatkov Date: Wed, 12 Oct 2016 09:59:14 +0300 Message-ID: Subject: Re: Evicted entry appears in Write-behind cache To: user@ignite.apache.org Content-Type: multipart/alternative; boundary=94eb2c0594baf99974053ea58726 archived-at: Wed, 12 Oct 2016 06:59:25 -0000 --94eb2c0594baf99974053ea58726 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi Pradeep, Could you please provide cache configuration? On Tue, Oct 11, 2016 at 6:57 PM, Denis Magda wrote: > Looks like that my initial understanding was wrong. There is a related > discussion > http://apache-ignite-users.70518.x6.nabble.com/Cache- > read-through-with-expiry-policy-td2521.html > > =E2=80=94 > Denis > > On Oct 11, 2016, at 8:55 AM, Pradeep Badiger > wrote: > > Hi Denis, > > I did the get() on the evicted entry from the cache, it still returned me > the value without calling the load() on the store. As you said, the entry > would be cached in the write behind store even for the evicted entry. Is > that true? > > Thanks, > Pradeep V.B. > *From:* Denis Magda [mailto:dmagda@gridgain.com ] > *Sent:* Monday, October 10, 2016 9:13 PM > *To:* user@ignite.apache.org > *Subject:* Re: Evicted entry appears in Write-behind cache > > Hi, > > How do you see that the evicted entries are still in the cache? If you > check this by calling cache get like operations then entries can be loade= d > back from the write-behind store or from your underlying store. > > =E2=80=94 > Denis > > > On Oct 8, 2016, at 1:00 PM, Pradeep Badiger > wrote: > > Hi, > > I am trying to evaluate Apache Ignite and trying to explore eviction > policy and write behind features. I am seeing that whenever a cache is > configured with eviction policy and write behind feature, the write behin= d > cache always have all the changed entries including the ones that are > evicted, before the write cache is flushed. But soon after it is flushed, > the store loads again from DB. Is this the expected behavior? Is there a > documentation on how the write behind cache works? > > Thanks, > Pradeep V.B. > This email and any files transmitted with it are confidential, proprietar= y > and intended solely for the individual or entity to whom they are > addressed. If you have received this email in error please delete it > immediately. > > > This email and any files transmitted with it are confidential, proprietar= y > and intended solely for the individual or entity to whom they are > addressed. If you have received this email in error please delete it > immediately. > > > --=20 Vladislav Pyatkov --94eb2c0594baf99974053ea58726 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi Pradeep,

Could you please prov= ide cache configuration?

On Tue, Oct 11, 2016 at 6:57 PM, Denis Magda <dmagda@gr= idgain.com> wrote:
Looks like that my initial understanding was wr= ong. There is a related discussion

=E2=80=94
D= enis

On Oct 11, 2016, at 8:55 AM, Pradeep Badiger <PradeepBadiger@fico.c= om> wrote:

Hi Denis,
= =C2=A0
I d= id the get() on the evicted entry from the cache, it still returned me the = value without calling the load() on the store. As you said, the entry would= be cached in the write behind store even for the evicted entry. Is that tr= ue?
=C2=A0<= u>
Thanks,
Pradeep V.B.
From:=C2=A0Denis Magd= a [mailto:dmagda@g= ridgain.com]=C2=A0
Sent:=C2=A0Monday, October 10, 2016 9:13 PM
To:<= span class=3D"m_-8147213174120302221Apple-converted-space">=C2=A0user@ignite.apache= .org
Subject:=C2=A0Re: Evicted entry appears in Write-behind cache=
=C2=A0=
Hi,
=C2=A0
= How do you see that the evicted entries are still in the cache? If you chec= k this by calling cache get like operations then entries can be loaded back= from the write-behind store or from your underlying store.=C2=A0=
=C2=A0
=
=E2=80=94
Denis
= =C2=A0
On Oct 8, 2016, at 1:00 PM, Pradeep Badiger= <PradeepBadiger@fico.com> wro= te:
=C2=A0
Hi,
= =C2=A0
I am trying to evalua= te Apache Ignite and trying to explore eviction policy and write behind fea= tures. I am seeing that whenever a cache is configured with eviction policy= and write behind feature, the write behind cache always have all the chang= ed entries including the ones that are evicted, before the write cache is f= lushed. But soon after it is flushed, the store loads again from DB. Is thi= s the expected behavior? Is there a documentation on how the write behind c= ache works?
=C2=A0=
Thanks,
Pradeep V.B.
This email and any files transmitted with it are confidential, proprietary= and intended solely for the individual or entity to whom they are addresse= d. If you have received this email in error please delete it immediately.
=C2=A0
This email and any files transmitted with it are confidential, propriet= ary and intended solely for the individual or entity to whom they are addre= ssed. If you have received this email in error please delete it immediately= .

<= /div>


--
Vladislav Pyatkov
--94eb2c0594baf99974053ea58726--