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 4B514200D20 for ; Tue, 3 Oct 2017 01:33:44 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 49DB4160BCB; Mon, 2 Oct 2017 23:33: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 9270C1609EF for ; Tue, 3 Oct 2017 01:33:43 +0200 (CEST) Received: (qmail 19404 invoked by uid 500); 2 Oct 2017 23:33: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 19395 invoked by uid 99); 2 Oct 2017 23:33:42 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Oct 2017 23:33:42 +0000 Received: from mail-lf0-f42.google.com (mail-lf0-f42.google.com [209.85.215.42]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id 6FAD11A00A6 for ; Mon, 2 Oct 2017 23:33:40 +0000 (UTC) Received: by mail-lf0-f42.google.com with SMTP id l23so903215lfk.10 for ; Mon, 02 Oct 2017 16:33:40 -0700 (PDT) X-Gm-Message-State: AHPjjUgHAjx9bCzyVtwAymvZCCk4jVf0DZ+pLy76C7y/K24fD8222BVM 6M7ndDQZR6tK1RwHdYPTKoCANfKhW+M3ZKKlTfVBHQ== X-Google-Smtp-Source: AOwi7QBukvYX35wrUAn8pE68li2+nGKYLzFZvR7bCR7+xcDtXW0lOiOi6CxLSK27qTQ+dN7o9yONZrZB1yaXe59V4Tc= X-Received: by 10.46.43.157 with SMTP id r29mr7703847ljr.56.1506987219025; Mon, 02 Oct 2017 16:33:39 -0700 (PDT) MIME-Version: 1.0 Received: by 10.25.209.69 with HTTP; Mon, 2 Oct 2017 16:33:38 -0700 (PDT) In-Reply-To: <1506964995093-0.post@n6.nabble.com> References: <1506774377698-0.post@n6.nabble.com> <1506964995093-0.post@n6.nabble.com> From: Alexey Kuznetsov Date: Tue, 3 Oct 2017 06:33:38 +0700 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Question about number of total onheap and offheap cache entries. To: user@ignite.apache.org Content-Type: multipart/alternative; boundary="94eb2c074a72df1605055a98cdab" archived-at: Mon, 02 Oct 2017 23:33:44 -0000 --94eb2c074a72df1605055a98cdab Content-Type: text/plain; charset="UTF-8" Hi Ray! Could you show your cache configuration? In case if you set "onHeapEnabled=true" Ignite will "cache" values in heap during get & sql operations. And heap metric will be > 0. As for 2.3 - it will be released by the end of October. You can always try to build from sources from master. https://ignite.apache.org/download.cgi#build-source On Tue, Oct 3, 2017 at 12:23 AM, Ray wrote: > Thank you Vasiliy for your answer. > > In the ticket, it looks like the problem is with the off-heap entry count. > But my question is why the on-heap entry count is always the same as the > off-heap entry count? > Ignite stores the cache off-heap by default, so in design there will be > zero > on-heap entry count when the cache is not visited, right? > Or is there some eviction configuration I need to set up for the entries to > be evicted after they are visited and brought on-heap? > I've been watching the visor stats for a day now, and the cache is not > visited during the day. > But the on-heap entry count is still not zero. > > And is there any release date for Ignite 2.3? > > Thanks > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ > -- Alexey Kuznetsov --94eb2c074a72df1605055a98cdab Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Ray!

Could you show your cache c= onfiguration?

In case if you set "onHeapEnabl= ed=3Dtrue" Ignite will "cache" values in heap during get &am= p; sql operations.
And heap metric will be > 0.

=
As for 2.3 - it will be released by the end of October.
You can always try to build from sources from master.


On Tue, Oct 3, 2017 at 1= 2:23 AM, Ray <rayliu@cisco.com> wrote:
Thank you Vasiliy for your answer.

In the ticket, it looks like the problem is with the off-heap entry count.<= br> But my question is why the on-heap entry count is always the same as the off-heap entry count?
Ignite stores the cache off-heap by default, so in design there will be zer= o
on-heap entry count when the cache is not visited, right?
Or is there some eviction configuration I need to set up for the entries to=
be evicted after they are visited and brought on-heap?
I've been watching the visor stats for a day now, and the cache is not<= br> visited during the day.
But the on-heap entry count is still not zero.

And is there any release date for Ignite 2.3?



--
=
Alexey Kuznetsov
=
--94eb2c074a72df1605055a98cdab--