From dev-return-31891-archive-asf-public=cust-asf.ponee.io@ignite.apache.org Mon Mar 12 22:09:03 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 34E5618064D for ; Mon, 12 Mar 2018 22:09:03 +0100 (CET) Received: (qmail 22702 invoked by uid 500); 12 Mar 2018 21:09:02 -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 22691 invoked by uid 99); 12 Mar 2018 21:09:02 -0000 Received: from mail-relay.apache.org (HELO mailrelay2-lw-us.apache.org) (207.244.88.137) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 12 Mar 2018 21:09:02 +0000 Received: from mail-qt0-f179.google.com (mail-qt0-f179.google.com [209.85.216.179]) by mailrelay2-lw-us.apache.org (ASF Mail Server at mailrelay2-lw-us.apache.org) with ESMTPSA id 506F01A67 for ; Mon, 12 Mar 2018 21:09:01 +0000 (UTC) Received: by mail-qt0-f179.google.com with SMTP id v90so20442966qte.12 for ; Mon, 12 Mar 2018 14:09:01 -0700 (PDT) X-Gm-Message-State: AElRT7EixU4lvJq4orEMp4ceWScMrrdbeXm889czsPzjQJ0c1EpelXED GcMhpitYfI1SQuKbGaUa2dXEPR0qlW9ckVJvB1PAqQ== X-Google-Smtp-Source: AG47ELsep61tsv+AqjQe3y5Cpa7pWgEPkKtLnmTTSj6t15EBTcEsAt7HIKwe6i1pB9OtoVJHEE2+3McXpraVDsWfqB4= X-Received: by 10.237.63.26 with SMTP id p26mr5141120qtf.104.1520888941069; Mon, 12 Mar 2018 14:09:01 -0700 (PDT) MIME-Version: 1.0 Received: by 10.12.185.143 with HTTP; Mon, 12 Mar 2018 14:03:21 -0700 (PDT) In-Reply-To: References: <2C96ED59-8CCF-4377-82FD-D2340EFF8C36@apache.org> <74B12DD3-6C79-418B-ACFB-4DEAA5D75B8C@apache.org> <338D46A4-EE27-4162-A493-C0E4BACECF26@apache.org> From: Denis Magda Date: Mon, 12 Mar 2018 14:03:21 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Data eviction/expiration from Ignite persistence To: dev@ignite.apache.org Cc: Alexey Goncharuk Content-Type: multipart/alternative; boundary="001a1140b77a135f5b05673d8d74" --001a1140b77a135f5b05673d8d74 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Dmitriy, It will break the current default behavior when data is evicted from the memory only, and I would disagree that it's a right decision overall. There are many scenarios when users need to have the eviction in the memory layer and preserve data on disk for later usage. So, can we keep what we have now and merely expand the eviction to disk if the user requires it? -- Denis On Mon, Mar 12, 2018 at 1:35 PM, Dmitry Pavlov wrote: > Denis, > > I suppose there is no configuration will be required. If TTL configured > entry will be removed from disk & memory both. > > SIncerely, > Dmitriy Pavlov > > =D0=BF=D0=BD, 12 =D0=BC=D0=B0=D1=80. 2018 =D0=B3. =D0=B2 23:32, Denis Mag= da : > > > Alexey, Dmitriy, > > > > What would be the configuration parameter that defines if the eviction > > should happen in the in-memory layer only or in both memory and disk? > > > > -- > > Denis > > > > On Mon, Mar 12, 2018 at 9:22 AM, Alexey Goncharuk < > > alexey.goncharuk@gmail.com> wrote: > > > > > Val, > > > > > > Yes, the entries will be removed from both memory and persistence. > > > > > > 2018-03-12 19:20 GMT+03:00 Valentin Kulichenko < > > > valentin.kulichenko@gmail.com>: > > > > > > > Alex, > > > > > > > > What is behavior going to be after IGNITE-5874 is fixed? Will expir= ed > > > entry > > > > be removed from both memory and persistence? > > > > > > > > -Val > > > > > > > > On Sat, Mar 10, 2018 at 12:06 AM, Alexey Goncharuk < > > > > alexey.goncharuk@gmail.com> wrote: > > > > > > > > > The ticket [1] is in patch available state looks good, the only > thing > > > > left > > > > > there is to transfer old entries to new storage. I hope Andrey wi= ll > > > have > > > > > time to finish this soon, so we can target the fix for 2.5. > > > > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-5874 > > > > > > > > > > 2018-03-09 22:51 GMT+03:00 Denis Magda : > > > > > > > > > > > Val, > > > > > > > > > > > > I'd like to hear Alexey G. opinion on this? Alex, please chime > in. > > > > > > > > > > > > In general, the more deployments the persistence will get the > more > > > > demand > > > > > > we will see for that capability. Personally, I'd create a ticke= t > > for > > > > now > > > > > > and put it off to our backlog. > > > > > > > > > > > > -- > > > > > > Denis > > > > > > > > > > > > > > > > > > On Fri, Mar 9, 2018 at 9:34 AM, Dmitriy Setrakyan < > > > > dsetrakyan@apache.org > > > > > > > > > > > > wrote: > > > > > > > > > > > > > On Fri, Mar 9, 2018 at 3:43 AM, Dmitry Pavlov < > > > dpavlov.spb@gmail.com > > > > > > > > > > > > wrote: > > > > > > > > > > > > > > > As far as I know there is no plans. Denis please correct me > if > > > I'm > > > > > > wrong. > > > > > > > > > > > > > > > > But users found these or similar bugs, it seems we need to > > > support > > > > > PDS > > > > > > > and > > > > > > > > TTL. > > > > > > > > > > > > > > > > > > > > > > We should either support it or throw a clear exception on > > startup > > > > > > clearly > > > > > > > stating that it is not. I suppose, it should be the latter fo= r > > now. > > > > > > > Dmitriy, any chance you can file a ticket for it? > > > > > > > > > > > > > > > > > > > > > > > > > > > > --001a1140b77a135f5b05673d8d74--