Mailing-List: contact dev-help@ignite.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ignite.apache.org
MIME-Version: 1.0
In-Reply-To: <0BFF7FA8-802B-4D6C-BEF3-725D7529C51D@gridgain.com>
References: <CAABS=BMZrxPwPMadVoYB8MyjShSijE6_iyFrWVw4bhgOtbx_bQ@mail.gmail.com>
 <CA+eZwrFWBoqaqOy7Ym9zNxY+gfSUei_0pdZERBN1-e90VOh4HA@mail.gmail.com>
 <AE9695BF-0A49-44B0-8C78-117590D2CA81@gridgain.com> <CA+0=VoV5PKC+=YaRiQHExreL7mfbGBGKkAo9p_nJMpWzRuP7oQ@mail.gmail.com>
 <CA+eZwrH+MaS3GAKjnmuhMu3DX6sADvQ8TRDxq17A1SSDtFnupQ@mail.gmail.com> <0BFF7FA8-802B-4D6C-BEF3-725D7529C51D@gridgain.com>
From: Sergi Vladykin <sergi.vladykin@gmail.com>
Date: Sat, 5 Nov 2016 16:23:00 +0300
Message-ID: <CA+eZwrGP+7=_DpxAgf=E5Yz4h5oS8ONmYoAXsfCuF2ZXF7HE4Q@mail.gmail.com>
Subject: Re: Off-Heap SQL Indexes
To: dev@ignite.apache.org
Cc: Sergi Vladykin <svladykin@gridgain.com>
Content-Type: multipart/alternative; boundary=001a11c01bca02489605408db366
archived-at: Sat, 05 Nov 2016 13:23:49 -0000

--001a11c01bca02489605408db366
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Your final statement seems correct to me, but I said exactly that, I don't
know where did you get that setOffHeapMaxMemory must be 0. May be you use
some weird email client which renders >> signs wrong?

Sergi

2016-11-04 22:25 GMT+03:00 Denis Magda <dmagda@gridgain.com>:

> Sergi,
>
> Thanks, now I found the exact conditions that switch the indexes from
> on-heap to off-heap.
>
> But looks like you did a misprint in your conclusion saying that
> setOffHeapMaxMemory should be 0.
> > Thus from the user standpoint we can say, that if either
> setOffHeapMaxMemory
> >> =3D 0 or setMemoryMode is set to any of off-heap modes, then indexes w=
ill
> go
> > off-heap.
>
> In fact, as you elaborated earlier, it has to be >=3D 0 which leads to th=
e
> following final statement:
>
> SQL engine will store indexes in the off-heap region if
> setOffHeapMaxMemory parameter >=3D 0 or setMemoryMode is set to any suppo=
rted
> off-heap mode. It worth to mention that setOffHeapMaxMemory is set to 0
> automatically if it=E2=80=99s value is less than -1 and one of off-heap m=
emory
> modes is used.
>
> Are we on the same page now?
>
> =E2=80=94
> Denis
>
> > On Nov 4, 2016, at 1:51 AM, Sergi Vladykin <sergi.vladykin@gmail.com>
> wrote:
> >
> > Denis,
> >
> > I checked the code now as well. I actually was wrong, but your statemen=
t
> is
> > wrong either.
> >
> > If we are talking about indexes then the exact condition when index wil=
l
> be
> > off-heap is the following: either setOffHeapMaxMemory >=3D 0 or
> setMemoryMode
> > is OFFHEAP_TIERED.
> >
> > But if setMemoryMode is set to one of off-heap modes and
> setOffHeapMaxMemory is
> > -1, then setOffHeapMaxMemory is silently getting switched to 0.
> >
> > Thus from the user standpoint we can say, that if either
> setOffHeapMaxMemory
> >> =3D 0 or setMemoryMode is set to any of off-heap modes, then indexes w=
ill
> go
> > off-heap.
> >
> > Sergi
> >
> > 2016-11-04 6:30 GMT+03:00 Dmitriy Setrakyan <dsetrakyan@apache.org>:
> >
> >> Do we currently throw an exception if memory mode is set to off-heap b=
y
> the
> >> max-offheap-memory is set to "-1"? Otherwise, it can get very confusin=
g
> to
> >> users.
> >>
> >> On Thu, Nov 3, 2016 at 10:22 AM, Denis Magda <dmagda@gridgain.com>
> wrote:
> >>
> >>> Sergi,
> >>>
> >>> Referring to your response and the source code I should say that, in
> >> fact,
> >>> the documentation has to state the following:
> >>>
> >>> =E2=80=9CTo place both data and indexes in off heap memory CacheConfi=
guration.
> >> setMemoryMode
> >>> has to be set to one of off heap modes and CacheConfiguration.
> >> setOffHeapMaxMemory
> >>> has to be set to a value different from -1 (disabled). If at least on=
e
> of
> >>> these conditions is not met then both data and indexes will be locate=
d
> in
> >>> on heap memory=E2=80=9D
> >>>
> >>> Is this statement correct?
> >>>
> >>> =E2=80=94
> >>> Denis
> >>>
> >>>> On Nov 3, 2016, at 2:53 AM, Sergi Vladykin <sergi.vladykin@gmail.com=
>
> >>> wrote:
> >>>>
> >>>> Prachi,
> >>>>
> >>>> In [2] we refer to the same CacheConfiguration.setOffHeapMaxMemory
> >>>> property, so [1] is correct. If setOffHeapMaxMemory is disabled (set
> to
> >>>> -1), then indexes will never be stored offheap, regardless of
> >>> setMemoryMode
> >>>> setting.
> >>>>
> >>>> Probably we have to change [2] to make it clear, that it is about
> >>>> setOffHeapMaxMemory
> >>>> but not about setMemoryMode.
> >>>>
> >>>> Sergi
> >>>>
> >>>>
> >>>> 2016-11-03 2:25 GMT+03:00 Prachi Garg <pgarg@gridgain.com>:
> >>>>
> >>>>> Engineers,
> >>>>>
> >>>>> I was going through documentation for Off-Heap SQL Indexes
> >>>>> <https://apacheignite.readme.io/docs/sql-queries#off-heap-
> sql-indexes
> >>>
> >>> and
> >>>>> found two contradicting statements-
> >>>>>
> >>>>> According to [1] -  " `CacheConfiguration.setOffHeapMaxMemory` is
> the
> >>> only
> >>>>> property to enable or disable off-heap indexing. While
> >>>>> CacheConfiguration.setMemoryMode is used to configure off-heap
> memory
> >>>>> <https://apacheignite.readme.io/v1.7/docs/off-heap-memory>, it does
> >> not
> >>>>> have any effect on indexing."
> >>>>>
> >>>>> According to [2] -  "Note that when off-heap memory is configured,
> >>> Ignite
> >>>>> will store query indexes off-heap as well."
> >>>>>
> >>>>>
> >>>>> Which one is true?
> >>>>>
> >>>>> [1] - https://apacheignite.readme.io/docs/sql-queries#off-heap-
> >>> sql-indexes
> >>>>>
> >>>>> [2] - http://apacheignite.gridgain.org/docs/off-heap-memory
> >>>>>
> >>>>>
> >>>>> Thanks,
> >>>>>
> >>>>> -Prachi
> >>>>>
> >>>
> >>>
> >>
>
>

--001a11c01bca02489605408db366--