From dev-return-30027-archive-asf-public=cust-asf.ponee.io@ignite.apache.org Sun Jan 14 05:13:15 2018 Return-Path: X-Original-To: archive-asf-public@eu.ponee.io Delivered-To: archive-asf-public@eu.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by mx-eu-01.ponee.io (Postfix) with ESMTP id 0423C180630 for ; Sun, 14 Jan 2018 05:13:15 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id DCFC1160C30; Sun, 14 Jan 2018 04:13:14 +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 2E0F6160C2F for ; Sun, 14 Jan 2018 05:13:14 +0100 (CET) Received: (qmail 45946 invoked by uid 500); 14 Jan 2018 04:13:13 -0000 Mailing-List: contact dev-help@ignite.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ignite.apache.org Delivered-To: mailing list dev@ignite.apache.org Received: (qmail 45935 invoked by uid 99); 14 Jan 2018 04:13:12 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 14 Jan 2018 04:13:12 +0000 Received: from mail-qk0-f171.google.com (mail-qk0-f171.google.com [209.85.220.171]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id 86C2B1A00E9 for ; Sun, 14 Jan 2018 04:13:10 +0000 (UTC) Received: by mail-qk0-f171.google.com with SMTP id d18so13348644qke.7 for ; Sat, 13 Jan 2018 20:13:10 -0800 (PST) X-Gm-Message-State: AKwxytdfmEFIaiefHsmW9SSL0g2fp8z4VtaxnSZvIxzLaOfGAbpZiiLC rx7/ejreWxoa22kCtfpouOPT1Br+axto6YmW3r6SSA== X-Google-Smtp-Source: ACJfBovONzGQ6phunkvfZjfhmSIjWLOVAlt01om7fKmecRXjXgLYtsFRHevigxxKaRt+b0ySqWR7/nIPm/L36e9TDGg= X-Received: by 10.55.188.129 with SMTP id m123mr42425368qkf.179.1515903188659; Sat, 13 Jan 2018 20:13:08 -0800 (PST) MIME-Version: 1.0 Received: by 10.140.36.133 with HTTP; Sat, 13 Jan 2018 20:12:27 -0800 (PST) In-Reply-To: References: <338929D4-51CD-49D3-86BC-230FF344515D@apache.org> From: Dmitriy Setrakyan Date: Sat, 13 Jan 2018 21:12:27 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: Fwd: Page eviction mode is ignored To: dev@ignite.apache.org Content-Type: multipart/alternative; boundary="94eb2c048e1c130bba0562b4b734" --94eb2c048e1c130bba0562b4b734 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Cross sending to dev@. Can anyone from committers review this patch? It is scheduled for 2.4 and there is not much time left. D. ---------- Forwarded message ---------- From: Sergey Sergeev Date: Tue, Jan 2, 2018 at 7:02 AM Subject: Re: Page eviction mode is ignored To: user@ignite.apache.org The similar issue was created by Denis, thanks. https://issues.apache.org/jira/browse/IGNITE-7347 On Sat, Dec 23, 2017 at 12:29 AM, Denis Magda wrote: > Hi Sergey, > > > But... page eviction doesn't work for "inMemory" memory region... Why? > > If Ignite persistence is enabled, then the page-based evictions have no > effect because the oldest pages will be purged from memory automatically. > > Updated the text of the warning to makes things clearer. > > > Does Ignite supports a mix (persistenceEnabled or not) of DataRegion > configurations? > > Yes, you can have the persistence enabled for region A and disabled for > region B. > > =E2=80=94 > Denis > > > > On Dec 22, 2017, at 1:13 PM, Sergey Sergeev > wrote: > > > > Hi, > > > > I'm confused. After the successful launch of the Ignite cluster version > 2.3.0, I saw the WARN message: > > WARN GridCacheDatabaseSharedManager - Page eviction mode for [inMemory= ] > memory region is ignored because Ignite Native Persistence is enabled > > > > Ignite spring config see below: > > > > ... > > > > ion"> > > > > > > > > guration.DataRegionConfiguration"> > > > > > > > > 1024}"/> > > > > > > > > > > guration.DataRegionConfiguration"> > > > > > > > > > > > > 1024}"/> > > > > guration.DataRegionConfiguration"> > > > > > > > > /> > > > > 1024}"/> > > > > > > > > > > > > ... > > > > > > > > But... page eviction doesn't work for "inMemory" memory region... Why? > > Does Ignite supports a mix (persistenceEnabled or not) of DataRegion > configurations? > > > > -- > > Best regards, > > Sergey S. Sergeev > > exit(0); > > --=20 =D0=A1 =D1=83=D0=B2=D0=B0=D0=B6=D0=B5=D0=BD=D0=B8=D0=B5=D0=BC, =D0=A1=D0=B5=D1=80=D0=B3=D0=B5=D0=B5=D0=B2 =D0=A1=D0=B5=D1=80=D0=B3=D0=B5= =D0=B9 (aka SSSerj) e-mail: webs.support@gmail.com =D0=B7=D0=B0=D0=BC=D0=B5=D1=82=D0=BA=D0=B8: https://twitter.com/ssserj exit(0); --94eb2c048e1c130bba0562b4b734--