Mailing-List: contact dev-help@ignite.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ignite.apache.org
MIME-Version: 1.0
References: <B722F7C6-6094-42FF-AE2A-7B74106CDC36@apache.org>
 <CA+0=VoWJ-P4ZAT+Ni183rFHg9xbFU7ohxC28Dg3-hphig_M1pQ@mail.gmail.com>
 <37bcdef8-15d3-d7c5-45a7-b8ee003a372e@gmail.com> <CAGcMBHj93J7MOeFy+neeGFZjnQXRt=Z6O-EHCvF=UoeEPspfeA@mail.gmail.com>
 <CAAoNTuG4NyZgOptZFuS9R7J+=46uP5L1Wrq_Ddae7fgiV7BQCQ@mail.gmail.com>
 <CA+0=VoX0wtaTSUXinGSATk99-8at0OHq-HqW8UtmfUMbtTt=Zw@mail.gmail.com>
 <CAMbfdjb3-Nb+Qe1JvE4K4JfFrPbMTCSTjegkEa1iuSrykTeW=A@mail.gmail.com>
 <CAAoNTuEdmKyRfPekwANvO10wRhvcSrjPadKS5FxfBYxQbOGSiQ@mail.gmail.com>
 <CAAoNTuF79=_XH_fg9hoS0KDm8T5KGAJp=H649qmHH3Q+YyuEPQ@mail.gmail.com>
 <CA+0=VoWhhhHRJ9zT0AeVOAGrHDJSPAdjTUiiDWFgbT_tTgwGqQ@mail.gmail.com>
 <CAAoNTuFVB0qDY0B9g0rks9FUFaAw80m=hCWg5HDbm7MbE7QNHA@mail.gmail.com>
 <55FF3F2B-53CC-4CEB-9728-BE72A9227CC0@apache.org> <CA+0=VoUOxV1++GvUW0qFhzd3RTYSxJPpKG6cNGzrkPbEvCuryg@mail.gmail.com>
 <D50A62C4-324F-4F58-8238-121925FDEEA2@apache.org> <CAAoNTuGo7_dOd8UfRtR5ED7cfF8x5a0KEEJ01EVHwYb8KA=psg@mail.gmail.com>
 <CA+0=VoVo4tOdqi8ozaGLC2s3vCmZABfmvLgr4qjkco8NPMqDFw@mail.gmail.com>
 <CAAoNTuHyZ1LyYr=eS9BCTjGsDre2qzidL=vwAjxrOD0-qs1J1Q@mail.gmail.com>
 <CA+0=VoVoRGyy9OQRNT8QpAeFSMCg9hC_rjk4OMRBOW8XTE9wbg@mail.gmail.com>
 <CAAoNTuHcvRm33nm1o83atprbVEerBFEwg7j0sycgvdKU_GQPAA@mail.gmail.com>
 <CAOKDqC8CF7HtjWucBA8w9zb0mx-QmaQkr3tvF-PAOf9FDyKTOA@mail.gmail.com>
 <CAOKDqC8g3bkBchosQFHh0rFw2qaG6NqWM_FcHWpPJP=M-gaedw@mail.gmail.com>
 <6CD5CF2A-4919-4729-A982-F0F7985E2E1A@apache.org> <CAGt6o8nVLuZ2Lakyn=GFn1Y2NPggb4Ekpb19L9Va0qzbx_9X4w@mail.gmail.com>
 <CAOKDqC8nQSyahF-0XA3kLuVL-4aFNuBZ0fg6UURNpwb-oE9AYQ@mail.gmail.com> <284140A5-C6D5-43DA-8FA6-4F7F907711C4@apache.org>
In-Reply-To: <284140A5-C6D5-43DA-8FA6-4F7F907711C4@apache.org>
From: Vladimir Ozerov <vozerov@gridgain.com>
Date: Wed, 30 Aug 2017 18:55:04 +0000
Message-ID: <CAGt6o8=fgPNtbSSse8yjyzVQ6Ryxbcsy-Jc74dwVHQFV-TrX_w@mail.gmail.com>
Subject: Re: [DISCUSSION] Urgent Ignite bug fix release
To: dev@ignite.apache.org
Content-Type: multipart/alternative; boundary="f403043e3c5078b7360557fd113d"
archived-at: Wed, 30 Aug 2017 18:55:23 -0000

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

IGNITE-6128 is not merged yet. I already raised my concerns, please chime
in.

=D1=81=D1=80, 30 =D0=B0=D0=B2=D0=B3. 2017 =D0=B3. =D0=B2 21:45, Denis Magda=
 <dmagda@apache.org>:

> Have the all pre-release tests passed? If so, let=E2=80=99s kick off the =
vote.
>
> =E2=80=94
> Denis
>
> > On Aug 30, 2017, at 4:29 AM, Anton Vinogradov <avinogradov@gridgain.com=
>
> wrote:
> >
> > 1) Fixes for:
> > - https://issues.apache.org/jira/browse/IGNITE-6204
> > - https://issues.apache.org/jira/browse/IGNITE-6193
> > merged
> >
> > 2) https://issues.apache.org/jira/browse/IGNITE-6003 resolved as
> duplicate
> > to https://issues.apache.org/jira/browse/IGNITE-6182
> >
> > 3) Current list if issues related to release 2.2:
> >
> https://issues.apache.org/jira/issues/?jql=3Dproject%20%3D%20Ignite%20and=
%20fixVersion%20%3D%202.2
> >
> > On Wed, Aug 30, 2017 at 1:24 PM, Vladimir Ozerov <vozerov@gridgain.com>
> > wrote:
> >
> >> I looked at the code of IGNITE-6182 (memory policy suggestions), and I
> do
> >> not like it. Too complex. My proposal:
> >> 1) Do not take in count JVM heap. First, we do not need whether it wil=
l
> be
> >> really used or not. Second, we never checked it in heap-based Ignite
> 1.x,
> >> and never had a single compliant.
> >> 2) We need to sum up all memory policies and *checkpoint buffer size*.
> If
> >> it exceeds 80% of machine's RAM - print a warning
> >>
> >> On Mon, Aug 28, 2017 at 7:26 PM, Denis Magda <dmagda@apache.org> wrote=
:
> >>
> >>> Anton, thanks for stepping in! The tickets set looks complete for me!
> >>>
> >>> Let=E2=80=99s start the vote once the fixes are merged and tests pass=
.
> >>>
> >>> =E2=80=94
> >>> Denis
> >>>
> >>>> On Aug 28, 2017, at 7:19 AM, Anton Vinogradov <
> >> avinogradov@gridgain.com>
> >>> wrote:
> >>>>
> >>>> Igniters,
> >>>>
> >>>> Seems 2.2 is a urgent bugfix release, so it should be based on 2.1,
> >>>> In this case all other issues with fixVersion =3D 2.2 should be move=
d to
> >>> 2.3.
> >>>>
> >>>> Currently, I see 835 issues with fixVersion =3D 2.2
> >>>>
> >>>> Seems we should have only 4 issues with fixVersion =3D 2.2:
> >>>> - Change default max memory size from 80% to 20% -
> >>>> https://issues.apache.org/jira/browse/IGNITE-6182
> >>>> - Detecting low memory on ignite node startup -
> >>>> https://issues.apache.org/jira/browse/IGNITE-6003
> >>>> - Backport of improvements to checkpoint algorithm -
> >>>> https://issues.apache.org/jira/browse/IGNITE-????
> >>>> - ML profile is missing in 2.1 binary release -
> >>>> https://issues.apache.org/jira/browse/IGNITE-6193
> >>>>
> >>>> Please correct me in case I've missed something.
> >>>>
> >>>> Ivan,
> >>>>> Let's include to the release tickets with optimizations of
> >> checkpointing
> >>>> algorithm:
> >>>>> https://issues.apache.org/jira/browse/IGNITE-6178
> >>>>> https://issues.apache.org/jira/browse/IGNITE-6033
> >>>>> https://issues.apache.org/jira/browse/IGNITE-5961
> >>>>> This will help users who are experiencing problems with slow
> >>> checkpoints.
> >>>>> Also, let's include
> https://issues.apache.org/jira/browse/IGNITE-6183
> >>> to
> >>>> soften "Ignite node crashed in the middle of checkpoint" message as
> per
> >>>> discussion <
> >>>> http://apache-ignite-developers.2346864.n4.nabble.
> >>> com/Ignite-close-G-stop-name-true-Change-flag-cancel-to-
> >> false-td20473.html
> >>>>> .
> >>>>
> >>>> All of these issues should have fixVersion 2.3.
> >>>> Please create backport issue and link it to all necessary issues.
> >>>>
> >>>> P.s. I've created branch ignite-2.2, currently it equals to
> ignite-2.1.
> >>>>
> >>>> On Mon, Aug 28, 2017 at 4:05 PM, Anton Vinogradov <
> >>> avinogradov@gridgain.com>
> >>>> wrote:
> >>>>
> >>>>> Denis,
> >>>>>
> >>>>>> BTW, who is considered to be the release manager of this release?
> >>>>> I'll do it.
> >>>>>
> >>>>> On Mon, Aug 28, 2017 at 3:54 PM, Seliverstov Igor <
> >> gvvinblade@gmail.com
> >>>>
> >>>>> wrote:
> >>>>>
> >>>>>> Ok, the check happens at the node start time or on NODE_JOIN event
> >>>>>>
> >>>>>> in general it looks like:
> >>>>>>
> >>>>>> 1) calculate expected used memory =3D heap max + system cache max =
+
> all
> >>>>>> custom policies max + default policy size and put it into a node
> >>> attribute
> >>>>>>
> >>>>>> 2) get total physycal memory, calculate expected safe to be used
> >> memory
> >>>>>> amount (leave 4 gb min or 20% of available memory for OS)
> >>>>>>
> >>>>>> 3) if expected used memory + expected used memory of other nodes o=
n
> >> the
> >>>>>> host > than safe to be used memory amount, start calculating
> >>> suggestions
> >>>>>>
> >>>>>> 4) Each ignite instance needs at least 512mb heap + 40mb system
> >> cache +
> >>>>>> 100mb default polycy, if available memory is less we cannot sugges=
t
> >>>>>> anything reasonable, print warning, stop calculation.
> >>>>>>
> >>>>>> 5) check heap size (shouldn't exceed 30% of available memory
> >>> (total_memory
> >>>>>> - reserved for OS memory) * 30% for all JVMs, if it exeedes, sugge=
st
> >>> just
> >>>>>> calculated value or 512MB minimal)
> >>>>>>
> >>>>>> 6) check if system cache size changed, suggest default value if it=
's
> >> so
> >>>>>>
> >>>>>> 7) in case 100 mb * policies count < available memory, suggest usi=
ng
> >>>>>> default policy with max size equals to remaining memory (available=
 -
> >>> heap
> >>>>>> -
> >>>>>> system cache)
> >>>>>>
> >>>>>> 8) calculate new size for each memory policy ( it's user defined
> >> size *
> >>>>>> (remaining / (all_policies_size * nodes_cnt)); in proportion to
> >>>>>> remaining memory, devided by nodes number on the host or 100 mb
> >>> minimal)
> >>>>>>
> >>>>>> 9) print suggestions
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> 2017-08-28 15:10 GMT+03:00 Dmitriy Setrakyan <dsetrakyan@apache.or=
g
> >>> :
> >>>>>>
> >>>>>>> Igor, can you please describe the algorithm with all the
> thresholds?
> >>>>>>>
> >>>>>>> On Mon, Aug 28, 2017 at 4:56 AM, Seliverstov Igor <
> >>> gvvinblade@gmail.com
> >>>>>>>
> >>>>>>> wrote:
> >>>>>>>
> >>>>>>>> The suggestion here is based on initial settings, and it's so
> >> because
> >>>>>>> there
> >>>>>>>> is no other nodes on the host in the example.
> >>>>>>>>
> >>>>>>>> The algorithm tries to preserve the original ratio of memory
> >> policies
> >>>>>>>> keeping numbers reasonable (for example after some thresshold it
> >> will
> >>>>>>>> suggest not to use several memory policies if there is not enoug=
h
> >> of
> >>>>>>> memory
> >>>>>>>> for all of them) and taking into consideration nodes count on th=
e
> >>>>>> host,
> >>>>>>>> each jvm heap, needed memory for OS, etc
> >>>>>>>>
> >>>>>>>> 2017-08-28 14:38 GMT+03:00 Dmitriy Setrakyan <
> >> dsetrakyan@apache.org
> >>>> :
> >>>>>>>>
> >>>>>>>>> Looks good, but why in the example provided are we suggesting
> >> 8GB? 2
> >>>>>>>> nodes
> >>>>>>>>> with 8GB will completely exhaust the available memory. I would
> >>>>>> suggest
> >>>>>>> 6
> >>>>>>>> or
> >>>>>>>>> 7GB.
> >>>>>>>>>
> >>>>>>>>> Also, why 100MB for default policy. Anything under 1GB seems to=
o
> >>>>>> small.
> >>>>>>>>>
> >>>>>>>>> Can you please comment?
> >>>>>>>>>
> >>>>>>>>> D.
> >>>>>>>>>
> >>>>>>>>> On Mon, Aug 28, 2017 at 3:31 AM, Seliverstov Igor <
> >>>>>>> gvvinblade@gmail.com>
> >>>>>>>>> wrote:
> >>>>>>>>>
> >>>>>>>>>> One more example of possible warning:
> >>>>>>>>>>
> >>>>>>>>>> -----------------------------------------------------
> >>>>>>>>>> Excessive memory usage by Ignite node process (performance may
> >>>>>> drop)
> >>>>>>>>>> [requested=3D44613MB, available=3D15942MB].
> >>>>>>>>>>
> >>>>>>>>>> Please tune the folowing settings as suggested:
> >>>>>>>>>> MemoryPolicyConfiguration.initialSize for bigPlc: 8102MB
> >>>>>>>>>> MemoryPolicyConfiguration.maxSize     for bigPlc: 8102MB
> >>>>>>>>>> MemoryPolicyConfiguration.initialSize for dfltPlc: 100MB
> >>>>>>>>>> MemoryPolicyConfiguration.maxSize     for dfltPlc: 100MB
> >>>>>>>>>>
> >>>>>>>>>> Current settings:
> >>>>>>>>>> Java Heap  maxSize: 3543MB
> >>>>>>>>>> Java Heap initSize: 250MB
> >>>>>>>>>> MemoryPolicyConfiguration.initialSize for bigPlc: 256MB
> >>>>>>>>>> MemoryPolicyConfiguration.maxSize     for bigPlc: 40960MB
> >>>>>>>>>> MemoryPolicyConfiguration.initialSize for dfltPlc: 10MB
> >>>>>>>>>> MemoryPolicyConfiguration.maxSize     for dfltPlc: 10MB
> >>>>>>>>>> The overall expected memory usage by all Ignite nodes on the
> >>>>>> host:
> >>>>>>>>>> 44613MB
> >>>>>>>>>> -----------------------------------------------------
> >>>>>>>>>>
> >>>>>>>>>> Your thoughts?
> >>>>>>>>>>
> >>>>>>>>>> 2017-08-28 5:06 GMT+03:00 Denis Magda <dmagda@apache.org>:
> >>>>>>>>>>
> >>>>>>>>>>> Guys,
> >>>>>>>>>>>
> >>>>>>>>>>> ML lib profile is missing in 2.1 release! That must be fixed
> and
> >>>>>>>> rolled
> >>>>>>>>>>> out in this emergency release:
> >>>>>>>>>>> https://issues.apache.org/jira/browse/IGNITE-6193 <
> >>>>>>>>>>> https://issues.apache.org/jira/browse/IGNITE-6193>
> >>>>>>>>>>>
> >>>>>>>>>>> Oleg, Yuri, please step in and handle the issue.
> >>>>>>>>>>>
> >>>>>>>>>>> BTW, who is considered to be the release manager of this
> >>>>>> release?
> >>>>>>>>>>>
> >>>>>>>>>>> =E2=80=94
> >>>>>>>>>>> Denis
> >>>>>>>>>>>
> >>>>>>>>>>>> On Aug 25, 2017, at 2:29 PM, Dmitriy Setrakyan <
> >>>>>>>>> dsetrakyan@apache.org>
> >>>>>>>>>>> wrote:
> >>>>>>>>>>>>
> >>>>>>>>>>>> I like the format proposed by Denis, very clear.
> >>>>>>>>>>>>
> >>>>>>>>>>>> However, I also do not understand why a user should change t=
he
> >>>>>>> size
> >>>>>>>>> of
> >>>>>>>>>>> some
> >>>>>>>>>>>> system cache. How would a user ever know what value to put
> >>>>>> there?
> >>>>>>>>> This
> >>>>>>>>>>>> value should be configured by Ignite automatically.
> >>>>>>>>>>>>
> >>>>>>>>>>>> D.
> >>>>>>>>>>>>
> >>>>>>>>>>>> On Fri, Aug 25, 2017 at 2:24 PM, Denis Magda <
> >>>>>> dmagda@apache.org>
> >>>>>>>>>> wrote:
> >>>>>>>>>>>>
> >>>>>>>>>>>>> Igor,
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> Let me suggest this format.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> ---------------------------------------------
> >>>>>>>>>>>>> Excessive memory usage by Ignite node process (performance
> >>>>>> may
> >>>>>>>> drop)
> >>>>>>>>>>>>> [requested=3D29251MB, available=3D15942MB]
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> Please tune the following settings:
> >>>>>>>>>>>>> [MemoryConfiguration.defaultMemoryPolicySize =3D suggested
> >>>>>>> value]
> >>>>>>>>>>>>> MemoryConfiguration.systemCacheMaxSize =3D suggested value
> >>>>>>>>>>>>> [MemoryPolicyConfiguration.maxSize for {policy_name_1} =3D
> >>>>>>>> suggested
> >>>>>>>>>>>>> value]
> >>>>>>>>>>>>> [MemoryPolicyConfiguration.maxSize for {policy_name_2} =3D
> >>>>>>>> suggested
> >>>>>>>>>>>>> value]
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> Current settings:
> >>>>>>>>>>>>> [DefaultMemoryPolicySize =3D value]
> >>>>>>>>>>>>> [{policy_name_1} size =3D value]
> >>>>>>>>>>>>> [{policy_name_1} size =3D value]
> >>>>>>>>>>>>> SystemCacheInitialSize =3D value
> >>>>>>>>>>>>> SystemCacheMaxSize =3D value
> >>>>>>>>>>>>> Java Heap Init Size =3D value
> >>>>>>>>>>>>> Java Heap Max Size =3D value
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> The overall memory usage by all Ignite nodes on the host:
> >>>>>> value
> >>>>>>>>>>>>> -------------------------------------------
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> Records in [=E2=80=A6] are optional. If custom memory polic=
y is not
> >>>>>> set
> >>>>>>> or
> >>>>>>>>> the
> >>>>>>>>>>>>> default memory policy is overridden the output will miss
> >>>>>> some of
> >>>>>>>> the
> >>>>>>>>>>> rows.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> As for systemCacheMaxSize, it should be show ONLY if the
> >>>>>>> parameter
> >>>>>>>>> was
> >>>>>>>>>>> set
> >>>>>>>>>>>>> explicitly by user code. Otherwise, the platform should be
> >>>>>> wise
> >>>>>>>>> enough
> >>>>>>>>>>> to
> >>>>>>>>>>>>> instantiate it properly depending on the host memory usage.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> =E2=80=94
> >>>>>>>>>>>>> Denis
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>> On Aug 25, 2017, at 1:49 PM, Seliverstov Igor <
> >>>>>>>>> gvvinblade@gmail.com>
> >>>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> The message without logging layout:
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> Not enough memory for current process [required=3D29251MB,
> >>>>>>>>>>>>> available=3D15942MB].
> >>>>>>>>>>>>>> Please change MemoryConfiguration.systemCacheMaxSize and
> >>>>>>>>>>>>>> MemoryConfiguration.defaultMemoryPolicySize to decrease
> >>>>>> memory
> >>>>>>>>>>> allocated
> >>>>>>>>>>>>>> for each node.
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> Current settings:
> >>>>>>>>>>>>>> HeapInit=3D250MB
> >>>>>>>>>>>>>> HeapMax=3D3543MB
> >>>>>>>>>>>>>> DefaultMemoryPolicySize=3D12753MB
> >>>>>>>>>>>>>> SystemCacheInitialSize=3D40MB
> >>>>>>>>>>>>>> SystemCacheMaxSize=3D100MB
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> Other ignite instanses on the server require: 12853MB
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> I think it's make sense to describe what these numbers are
> >>>>>>>> consist
> >>>>>>>>>> of.
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> We simple say which parameters have an impact on how much
> >>>>>>> memory
> >>>>>>>>> the
> >>>>>>>>>>>>>> instance needs and their (parameters) actual values.
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> Also we notice that more than one Ignite instance are ran =
on
> >>>>>>> the
> >>>>>>>>>> server
> >>>>>>>>>>>>> or
> >>>>>>>>>>>>>> workstation and it also consumes memory.
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> 25 =D0=B0=D0=B2=D0=B3. 2017 =D0=B3. 21:30 =D0=BF=D0=BE=D0=
=BB=D1=8C=D0=B7=D0=BE=D0=B2=D0=B0=D1=82=D0=B5=D0=BB=D1=8C "Dmitriy Setrakya=
n" <
> >>>>>>>>>>>>>> dsetrakyan@apache.org> =D0=BD=D0=B0=D0=BF=D0=B8=D1=81=D0=
=B0=D0=BB:
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> Igor, what is this flood of WARN messaging coming after t=
he
> >>>>>>>> text?
> >>>>>>>>>> Are
> >>>>>>>>>>> we
> >>>>>>>>>>>>>>> really going to print this whole thing out?
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> On Fri, Aug 25, 2017 at 9:49 AM, Seliverstov Igor <
> >>>>>>>>>>> gvvinblade@gmail.com
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> This message appears on topology change in case the
> >>>>>> available
> >>>>>>>>>> memory
> >>>>>>>>>>> is
> >>>>>>>>>>>>>>>> exceeded
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> 2017-08-25 19:47 GMT+03:00 Seliverstov Igor <
> >>>>>>>>> gvvinblade@gmail.com
> >>>>>>>>>>> :
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> An example of current impl:
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> [2017-08-25 19:44:37,740][WARN ][disco-event-worker-#29=
%
> >>>>>>>>> internal.
> >>>>>>>>>>>>>>>>> GridHomePathSelfTest0%][GridDiscoveryManager]
> >>>>>>>>>>>>>>>>> [2017-08-25 19:44:37,740][WARN ][disco-event-worker-#29=
%
> >>>>>>>>> internal.
> >>>>>>>>>>>>>>>>> GridHomePathSelfTest0%][GridDiscoveryManager] Not enoug=
h
> >>>>>>>> memory
> >>>>>>>>>> for
> >>>>>>>>>>>>>>>>> current process [required=3D29251MB, available=3D15942M=
B].
> >>>>>>>>>>>>>>>>> [2017-08-25 19:44:37,740][WARN ][disco-event-worker-#29=
%
> >>>>>>>>> internal.
> >>>>>>>>>>>>>>>>> GridHomePathSelfTest0%][GridDiscoveryManager] Please
> >>>>>> change
> >>>>>>>>>>>>>>>>> MemoryConfiguration.systemCacheMaxSize and
> >>>>>>>> MemoryConfiguration.
> >>>>>>>>>>>>>>>> defaultMemoryPolicySize
> >>>>>>>>>>>>>>>>> to decrease memory allocated for each node.
> >>>>>>>>>>>>>>>>> [2017-08-25 19:44:37,740][WARN ][disco-event-worker-#29=
%
> >>>>>>>>> internal.
> >>>>>>>>>>>>>>>>> GridHomePathSelfTest0%][GridDiscoveryManager]
> >>>>>>>>>>>>>>>>> [2017-08-25 19:44:37,740][WARN ][disco-event-worker-#29=
%
> >>>>>>>>> internal.
> >>>>>>>>>>>>>>>>> GridHomePathSelfTest0%][GridDiscoveryManager] Current
> >>>>>>>> settings:
> >>>>>>>>>>>>>>>>> [2017-08-25 19:44:37,740][WARN ][disco-event-worker-#29=
%
> >>>>>>>>> internal.
> >>>>>>>>>>>>>>>>> GridHomePathSelfTest0%][GridDiscoveryManager]
> >>>>>>>> HeapInit=3D250MB
> >>>>>>>>>>>>>>>>> [2017-08-25 19:44:37,741][WARN ][disco-event-worker-#29=
%
> >>>>>>>>> internal.
> >>>>>>>>>>>>>>>>> GridHomePathSelfTest0%][GridDiscoveryManager]
> >>>>>>>> HeapMax=3D3543MB
> >>>>>>>>>>>>>>>>> [2017-08-25 19:44:37,741][WARN ][disco-event-worker-#29=
%
> >>>>>>>>> internal.
> >>>>>>>>>>>>>>>>> GridHomePathSelfTest0%][GridDiscoveryManager]
> >>>>>>>>>>>>>>> DefaultMemoryPolicySize=3D
> >>>>>>>>>>>>>>>>> 12753MB
> >>>>>>>>>>>>>>>>> [2017-08-25 19:44:37,741][WARN ][disco-event-worker-#29=
%
> >>>>>>>>> internal.
> >>>>>>>>>>>>>>>>> GridHomePathSelfTest0%][GridDiscoveryManager]
> >>>>>>>>>>>>>>>>> SystemCacheInitialSize=3D40MB
> >>>>>>>>>>>>>>>>> [2017-08-25 19:44:37,741][WARN ][disco-event-worker-#29=
%
> >>>>>>>>> internal.
> >>>>>>>>>>>>>>>>> GridHomePathSelfTest0%][GridDiscoveryManager]
> >>>>>>>>>>>>>>> SystemCacheMaxSize=3D100MB
> >>>>>>>>>>>>>>>>> [2017-08-25 19:44:37,741][WARN ][disco-event-worker-#29=
%
> >>>>>>>>> internal.
> >>>>>>>>>>>>>>>>> GridHomePathSelfTest0%][GridDiscoveryManager]
> >>>>>>>>>>>>>>>>> [2017-08-25 19:44:37,741][WARN ][disco-event-worker-#29=
%
> >>>>>>>>> internal.
> >>>>>>>>>>>>>>>>> GridHomePathSelfTest0%][GridDiscoveryManager] Other
> >>>>>> ignite
> >>>>>>>>>>> instanses
> >>>>>>>>>>>>>>> on
> >>>>>>>>>>>>>>>>> the server require: 12853MB
> >>>>>>>>>>>>>>>>> [2017-08-25 19:44:37,741][WARN ][disco-event-worker-#29=
%
> >>>>>>>>> internal.
> >>>>>>>>>>>>>>>>> GridHomePathSelfTest0%][GridDiscoveryManager]
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> 2017-08-25 17:40 GMT+03:00 Sergey Kozlov <
> >>>>>>>> skozlov@gridgain.com
> >>>>>>>>>> :
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> I suppose we should not forget JVM heap size and
> >>>>>> suggest to
> >>>>>>>>>> reduce
> >>>>>>>>>>>>>>> both
> >>>>>>>>>>>>>>>>>> options
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> On Fri, Aug 25, 2017 at 5:24 PM, Dmitriy Setrakyan <
> >>>>>>>>>>>>>>>> dsetrakyan@apache.org
> >>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>> Igor, I would change the message. How about this:
> >>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>> Required RAM size is larger than total physical memor=
y
> >>>>>>>>> available
> >>>>>>>>>>> for
> >>>>>>>>>>>>>>>> OS.
> >>>>>>>>>>>>>>>>>>>> Please change MemoryConfiguration.WhichProperty and
> >>>>>>>>>>>>>>>>>>>> MemoryPolicyConfiguration.WhichProperty to decrease
> >>>>>>> memory
> >>>>>>>>>>>>>>>> allocated
> >>>>>>>>>>>>>>>>>> for
> >>>>>>>>>>>>>>>>>>>> each node.
> >>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>> Also, can we calculate what the memory size allocated
> >>>>>> for
> >>>>>>>> each
> >>>>>>>>>>> node
> >>>>>>>>>>>>>>>>>> should
> >>>>>>>>>>>>>>>>>>> be? In that case we should suggest it.
> >>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>> D.
> >>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>> On Fri, Aug 25, 2017 at 7:20 AM, Seliverstov Igor <
> >>>>>>>>>>>>>>>> gvvinblade@gmail.com
> >>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>> What do you, guys think about next warning?
> >>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>> [2017-08-25 17:17:04,718][INFO
> >>>>>>>>>>>>>>>>>>>> ][test-runner-#1%internal.GridHomePathSelfTest%][
> >>>>>>>> GridHomePat
> >>>>>>>>>>>>>>>>>> hSelfTest0]
> >>>>>>>>>>>>>>>>>>>> System cache's MemoryPolicy size is configured to 40
> >>>>>> MB.
> >>>>>>>> Use
> >>>>>>>>>>>>>>>>>>>> MemoryConfiguration.systemCacheMemorySize property t=
o
> >>>>>>>> change
> >>>>>>>>>> the
> >>>>>>>>>>>>>>>>>>> setting.
> >>>>>>>>>>>>>>>>>>>> [2017-08-25 17:17:04,718][WARN
> >>>>>>>>>>>>>>>>>>>> ][test-runner-#1%internal.GridHomePathSelfTest%][
> >>>>>>>> GridHomePat
> >>>>>>>>>>>>>>>>>> hSelfTest0]
> >>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>>>> Required RAM size is larger than total physical
> >>>>>> memory
> >>>>>>>>>>>>>>> available
> >>>>>>>>>>>>>>>>>> for
> >>>>>>>>>>>>>>>>>>>> OS.
> >>>>>>>>>>>>>>>>>>>>>>> Check your configuration to avoid swap partition
> >>>>>>> usage.
> >>>>>>>>>>>>>>>>>>>>>>> Use MemoryConfiguration and
> >>>>>> MemoryPolicyConfiguration
> >>>>>>> to
> >>>>>>>>>>>>>>> change
> >>>>>>>>>>>>>>>>>> the
> >>>>>>>>>>>>>>>>>>>> settings.
> >>>>>>>>>>>>>>>>>>>>>>> Physical memory [required=3D16397MB,
> >>>>>> available=3D15942MB]
> >>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>> [2017-08-25 17:17:04,726][WARN
> >>>>>>>>>>>>>>>>>>>> ][test-runner-#1%internal.GridHomePathSelfTest%][
> >>>>>>>> GridHomePat
> >>>>>>>>>>>>>>>>>> hSelfTest0]
> >>>>>>>>>>>>>>>>>>>> Peer class loading is enabled (disable it in
> >>>>>> production
> >>>>>>> for
> >>>>>>>>>>>>>>>>>> performance
> >>>>>>>>>>>>>>>>>>> and
> >>>>>>>>>>>>>>>>>>>> deployment consistency reasons)
> >>>>>>>>>>>>>>>>>>>> [2017-08-25 17:17:04,726][INFO
> >>>>>>>>>>>>>>>>>>>> ][test-runner-#1%internal.GridHomePathSelfTest%][
> >>>>>>>> GridHomePat
> >>>>>>>>>>>>>>>>>> hSelfTest0]
> >>>>>>>>>>>>>>>>>>>> Configured caches [in 'sysMemPlc' memoryPolicy:
> >>>>>>>>>>>>>>>> ['ignite-sys-cache']]
> >>>>>>>>>>>>>>>>>>>> [2017-08-25 17:17:04,731][INFO
> >>>>>>>>>>>>>>>>>>>> ][test-runner-#1%internal.GridHomePathSelfTest%][
> >>>>>>>> GridHomePat
> >>>>>>>>>>>>>>>>>> hSelfTest0]
> >>>>>>>>>>>>>>>>>>>> 3-rd party licenses can be found at:
> >>>>>>>>>>>>>>>>>>>> /home/gvvinblade/projects/igni
> >>>>>> te/incubator-ignite/libs/
> >>>>>>>>>> licenses
> >>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>> 2017-08-25 13:26 GMT+03:00 Yakov Zhdanov <
> >>>>>>>>> yzhdanov@apache.org
> >>>>>>>>>>> :
> >>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>> Agree, let's release new version including tickets
> >>>>>>>> mentioned
> >>>>>>>>>> by
> >>>>>>>>>>>>>>>>>> Denis
> >>>>>>>>>>>>>>>>>>> and
> >>>>>>>>>>>>>>>>>>>>> Ivan.
> >>>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>> --Yakov
> >>>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> --
> >>>>>>>>>>>>>>>>>> Sergey Kozlov
> >>>>>>>>>>>>>>>>>> GridGain Systems
> >>>>>>>>>>>>>>>>>> www.gridgain.com
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>
> >>>>>>>>
> >>>>>>>
> >>>>>>
> >>>>>
> >>>>>
> >>>
> >>>
> >>
>
>

--f403043e3c5078b7360557fd113d--