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 02FBF200C85 for ; Tue, 30 May 2017 20:25:31 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 015CB160BC9; Tue, 30 May 2017 18:25:31 +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 D2024160BB1 for ; Tue, 30 May 2017 20:25:28 +0200 (CEST) Received: (qmail 99054 invoked by uid 500); 30 May 2017 18:25:27 -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 99045 invoked by uid 99); 30 May 2017 18:25:27 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 30 May 2017 18:25:27 +0000 Received: from [192.168.75.184] (c-73-222-138-29.hsd1.ca.comcast.net [73.222.138.29]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id 5518F1A031B for ; Tue, 30 May 2017 18:25:27 +0000 (UTC) From: Denis Magda Content-Type: multipart/alternative; boundary="Apple-Mail=_B983C5FD-D4BC-4E71-BA21-E09D453817CB" Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: Ignite and Memory Info Date: Tue, 30 May 2017 11:25:26 -0700 References: <180E7701-739A-4085-8956-5B0C8FE96BEA@apache.org> <7AEA6956-95DE-40F1-8C63-65E2D28EE9B3@apache.org> To: user@ignite.apache.org In-Reply-To: Message-Id: X-Mailer: Apple Mail (2.3273) archived-at: Tue, 30 May 2017 18:25:31 -0000 --Apple-Mail=_B983C5FD-D4BC-4E71-BA21-E09D453817CB Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 It depends on the community. But I think close to the end of June is = more realistic than the beginning. =E2=80=94 Denis > On May 30, 2017, at 11:22 AM, Lukas Lentner = wrote: >=20 > Begin or end ? ;-)))))) > =20 > =20 > ---- > =20 > Lukas Lentner, B. Sc. > St.-Cajetan-Stra=C3=9Fe 13 > 81669 M=C3=BCnchen > Deutschland > Fon: +49 / 89 / 71 67 44 96 > Mobile: +49 / 176 / 24 77 09 22 > E-Mail: Kontakt@LukasLentner.de > Website: www.LukasLentner.de > =20 > IBAN: DE33 7019 0000 0001 1810 17 > BIC: GENODEF1M01 (M=C3=BCnchner Bank) > =20 > Von: Denis Magda [mailto:dmagda@apache.org]=20 > Gesendet: Dienstag, 30. Mai 2017 20:21 > An: user@ignite.apache.org > Betreff: Re: Ignite and Memory Info > =20 > It should be release in June. > =20 > =E2=80=94 > Denis > =20 > On May 30, 2017, at 11:17 AM, Lukas Lentner > wrote: > =20 > You wrote in the post before that it could go into 2.1 =E2=80=A6 > =20 > My question is: When will 2.1 come and will it be in there =E2=80=A6 > =20 > ;-) > Bye > Lukas > =20 > =20 > ---- > =20 > Lukas Lentner, B. Sc. > St.-Cajetan-Stra=C3=9Fe 13 > 81669 M=C3=BCnchen > Deutschland > Fon: +49 / 89 / 71 67 44 96 > Mobile: +49 / 176 / 24 77 09 22 > E-Mail: Kontakt@LukasLentner.de > Website: www.LukasLentner.de > =20 > IBAN: DE33 7019 0000 0001 1810 17 > BIC: GENODEF1M01 (M=C3=BCnchner Bank) > =20 > Von: Dmitry Pavlov [mailto:dpavlov.spb@gmail.com = ]=20 > Gesendet: Dienstag, 30. Mai 2017 18:38 > An: user@ignite.apache.org > Betreff: Re: Ignite and Memory Info > =20 > Hi, > =20 > I am not sure I understand your question. Issue in JIRA is not yet = assigned to version. > =20 > Best Regards, > Dmitriy Pavlov > =20 > =D0=B2=D1=82, 30 =D0=BC=D0=B0=D1=8F 2017 =D0=B3. =D0=B2 12:52, Lukas = Lentner >: > Hi, > =20 > what is date of the fixed version? > =20 > Thankx > Lukas > =20 > =20 > ---- > =20 > Lukas Lentner, B. Sc. > St.-Cajetan-Stra=C3=9Fe 13 > 81669 M=C3=BCnchen > Deutschland > Fon: +49 / 89=C2=A0 / 71 67 44 96 > Mobile: +49 / 176 / 24 77 09 22 > E-Mail: Kontakt@LukasLentner.de > Website: www.LukasLentner.de > =20 > IBAN: DE33 7019 0000 0001 1810 17 > BIC: GENODEF1M01 (M=C3=BCnchner Bank) > =20 > Von: Dmitry Pavlov [mailto:dpavlov.spb@gmail.com = ]=20 > Gesendet: Mittwoch, 24. Mai 2017 20:23 >=20 > An: user@ignite.apache.org > Betreff: Re: Ignite and Memory Info > =20 > Denis, > =20 > To my mind it could be fixed, there should be not so much code to = change. > =20 > Best Regards, > Dmitriy Pavlov > =20 > =D1=81=D1=80, 24 =D0=BC=D0=B0=D1=8F 2017 =D0=B3. =D0=B2 21:13, Denis = Magda >: > Dmitriy, > =20 > Can this be fixed in 2.1? It looks like a serious bug to me. > =20 > =E2=80=94 > Denis > =20 > On May 24, 2017, at 10:59 AM, Lukas Lentner > wrote: > =20 > Is there any possible workaround? It pretty much makes me unable to = use ignite right now=E2=80=A6 > It is a real dealbreaker ;-)) > =20 > =20 > ---- > =20 > Lukas Lentner, B. Sc. > St.-Cajetan-Stra=C3=9Fe 13 > 81669 M=C3=BCnchen > Deutschland > Fon: +49 / 89=C2=A0 / 71 67 44 96 > Mobile: +49 / 176 / 24 77 09 22 > E-Mail: Kontakt@LukasLentner.de > Website: www.LukasLentner.de > =20 > IBAN: DE33 7019 0000 0001 1810 17 > BIC: GENODEF1M01 (M=C3=BCnchner Bank) > =20 > Von: Dmitry Pavlov [mailto:dpavlov.spb@gmail.com = ]=20 > Gesendet: Mittwoch, 24. Mai 2017 19:35 > An: user@ignite.apache.org > Betreff: Re: Ignite and Memory Info > =20 > Hi Lukas, > =20 > I have created improvement = https://issues.apache.org/jira/browse/IGNITE-5288 = to consider this = suggestion in future versions. > =20 > Best Regards, > Dmitry Pavlov > =20 > =D1=81=D1=80, 24 =D0=BC=D0=B0=D1=8F 2017 =D0=B3. =D0=B2 15:39, Lukas = Lentner >: > Hi, > =20 > When using Ignite 1.7 together with Excelsior JET Ahead-Of-Time = Compiler we get this error on various occasions: > =20 > java.lang.IllegalArgumentException: committed =3D 5274103808 should be = < max =3D 5274095616 > at java.lang.management.MemoryUsage.(Unknown Source) > at sun.management.MemoryImpl.(Unknown Source) > at sun.management.MemoryImpl.getHeapMemoryUsage(Unknown = Source) > at = org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$6.getHe= apMemoryCommitted(GridDiscoveryManager.java:778) > at = org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$7.metri= cs(GridDiscoveryManager.java:878) > at = org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processHe= artbeatMessage(ServerImpl.java:4651) > at = org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processMe= ssage(ServerImpl.java:2325) > at = org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processMe= ssage(ServerImpl.java:2135) > at = org.apache.ignite.spi.discovery.tcp.ServerImpl$MessageWorkerAdapter.body(S= erverImpl.java:6123) > at = org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.body(Serv= erImpl.java:2222) > at = org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62) > =20 > For me it looks like, that the commited and the max memory numbers are = not consistent and getHeapMemoryUsage() throws a IllegalArgumentEx about = it. > =20 > I found this error on various other software issue tracker as = netbeans, =E2=80=A6 and my impression is, that it is common. So = GridDiscoveryManager should think about the possibility to get such = error and not kill the whole process because of it. > =20 > What do you think? Do you have the same error sometimes? > =20 > Bye > Lukas > =20 > =20 > =20 > ---- > =20 > Lukas Lentner, B. Sc. > St.-Cajetan-Stra=C3=9Fe 13 > 81669 M=C3=BCnchen > Deutschland > Fon: +49 / 89=C2=A0 / 71 67 44 96 > Mobile: +49 / 176 / 24 77 09 22 > E-Mail: Kontakt@LukasLentner.de > Website: www.LukasLentner.de > =20 > IBAN: DE33 7019 0000 0001 1810 17 > BIC: GENODEF1M01 (M=C3=BCnchner Bank) --Apple-Mail=_B983C5FD-D4BC-4E71-BA21-E09D453817CB Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 It depends on the community. But I think close to the end of = June is more realistic than the beginning.

=E2=80=94
Denis

On May 30, 2017, at 11:22 AM, = Lukas Lentner <kontakt@lukaslentner.de> wrote:

Begin or end ? = ;-))))))
 
 
----
 
Lukas Lentner, B. Sc.
St.-Cajetan-Stra=C3=9Fe 13
81669 = M=C3=BCnchen
Deutschland
Fon:     +49 / 89  / 71 67 44 96
Mobile:  +49 / 176 / 24 77 09 22
 
IBAN:    DE33 7019 0000 0001 1810 17
BIC:     GENODEF1M01 (M=C3=BCnchner = Bank)
 
Von: Denis Magda [mailto:dmagda@apache.org] 
Gesendet: Dienstag, 30. Mai 2017 = 20:21
An: user@ignite.apache.org
Betreff: Re: Ignite and Memory = Info
 
It should be release in June.
 
=E2=80=94
Denis
 
On = May 30, 2017, at 11:17 AM, Lukas Lentner <kontakt@lukaslentner.de> = wrote:
 
You wrote in the post before that it could = go into 2.1 =E2=80=A6
 
My question = is: When will 2.1 come and will it be in there =E2=80=A6
 
;-)
Bye
Lukas
 
 
----
 
Lukas = Lentner, B. Sc.
St.-Cajetan-Stra=C3=9Fe 13
81669 M=C3=BCnchen
Deutschland
Fon:     +49 / 89  / 71 67 44 = 96
Mobile:  +49 / 176 / 24 77 = 09 22
 
IBAN:    DE33 7019 0000 0001 1810 = 17
BIC:     = GENODEF1M01 (M=C3=BCnchner Bank)
 
Von: Dmitry Pavlov [mailto:dpavlov.spb@gmail.com] 
Gesendet: Dienstag, 30. Mai 2017 = 18:38
An: user@ignite.apache.org
Betreff: Re: Ignite and Memory = Info
 
Hi,
 
I am = not sure I understand your question. Issue in JIRA is not yet assigned = to version.
 
Best Regards,
Dmitriy Pavlov
 
=D0=B2=D1=82, 30 = =D0=BC=D0=B0=D1=8F 2017 =D0=B3. =D0=B2 12:52, Lukas Lentner <kontakt@lukaslentner.de>:
Hi,
 
what is date = of the fixed version?
 
Thankx
Lukas
 
 
----
 
Lukas = Lentner, B. Sc.
St.-Cajetan-Stra=C3=9Fe 13
81669 M=C3=BCnchen
Deutschland
 
IBAN:    DE33 7019 0000 0001 1810 = 17
BIC:     = GENODEF1M01 (M=C3=BCnchner Bank)
 
Von: Dmitry Pavlov [mailto:dpavlov.spb@gmail.com] 
Gesendet: Mittwoch, 24. Mai 2017 = 20:23

An: user@ignite.apache.org
Betreff: Re: Ignite and Memory = Info
 
Denis,
 
To my mind it could be fixed, there = should be not so much code to change.
 
Best Regards,
Dmitriy Pavlov
 
=D1=81=D1=80, 24 =D0=BC=D0=B0=D1=8F 2017 =D0=B3. =D0=B2 = 21:13, Denis Magda <dmagda@apache.org>:
Dmitriy,
 
Can this be fixed in 2.1? It looks like a = serious bug to me.
 
=E2=80=94
Denis
 
On May 24, 2017, at 10:59 AM, Lukas = Lentner <kontakt@lukaslentner.de>= wrote:
 
Is there any possible = workaround? It pretty much makes me unable to use ignite right = now=E2=80=A6
It is a real = dealbreaker ;-))
 
 
----
 
Lukas Lentner, B. = Sc.
St.-Cajetan-Stra=C3=9Fe 13
81669 M=C3=BCnchen
Deutschland
 
IBAN:    DE33 = 7019 0000 0001 1810 17
BIC:     GENODEF1M01 (M=C3=BCnchner = Bank)
 
Von: Dmitry Pavlov [mailto:dpavlov.spb@gmail.com] 
Gesendet: Mittwoch, 24. Mai 2017 19:35
An: user@ignite.apache.org
Betreff: Re: Ignite and Memory Info
 
Hi Lukas,
 
I = have created improvement https://issues.apache.org/jira/browse/IGNITE-5288&nb= sp;to consider this suggestion in future versions.
 
Best Regards,
Dmitry Pavlov
 
=D1=81= =D1=80, 24 =D0=BC=D0=B0=D1=8F 2017 =D0=B3. =D0=B2 15:39, Lukas Lentner = <kontakt@lukaslentner.de>:
Hi,
 
When using Ignite 1.7 together with Excelsior = JET Ahead-Of-Time Compiler we get this error on various = occasions:
 
java.lang.IllegalArgumentException: committed =3D 5274103808 = should be < max =3D 5274095616
        at = java.lang.management.MemoryUsage.<init>(Unknown Source)
        at = sun.management.MemoryImpl.<unknown>(Unknown Source)
        at = sun.management.MemoryImpl.getHeapMemoryUsage(Unknown Source)
        at = org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$6.getHe= apMemoryCommitted(GridDiscoveryManager.java:778)
        at = org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$7.metri= cs(GridDiscoveryManager.java:878)
        at = org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processHe= artbeatMessage(ServerImpl.java:4651)
        at = org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processMe= ssage(ServerImpl.java:2325)
        at = org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processMe= ssage(ServerImpl.java:2135)
        at = org.apache.ignite.spi.discovery.tcp.ServerImpl$MessageWorkerAdapter.body(S= erverImpl.java:6123)
        at = org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.body(Serv= erImpl.java:2222)
        at = org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)<= o:p class=3D"">
 
For me it looks like, that the commited and = the max memory numbers are not consistent and getHeapMemoryUsage() = throws a IllegalArgumentEx about it.
 
I found this error on various other software = issue tracker as netbeans, =E2=80=A6 and my impression is, that it is = common. So GridDiscoveryManager should think about the possibility to = get such error and not kill the whole process because of it.
 
What do you think? Do you have the same error = sometimes?
 
Bye
Lukas
 
 
 
----
 
Lukas Lentner, B. = Sc.
St.-Cajetan-Stra=C3=9Fe 13
81669 M=C3=BCnchen
Deutschland
 
IBAN:    DE33 = 7019 0000 0001 1810 17
BIC:     GENODEF1M01 (M=C3=BCnchner = Bank)
<= /div>
<= /div>
<= /div>
= --Apple-Mail=_B983C5FD-D4BC-4E71-BA21-E09D453817CB--