From user-return-26688-archive-asf-public=cust-asf.ponee.io@ignite.apache.org Wed Jul 24 23:29:27 2019 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 [207.244.88.153]) by mx-eu-01.ponee.io (Postfix) with SMTP id 3423718025F for ; Thu, 25 Jul 2019 01:29:27 +0200 (CEST) Received: (qmail 88196 invoked by uid 500); 24 Jul 2019 23:29:25 -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 88185 invoked by uid 99); 24 Jul 2019 23:29:25 -0000 Received: from Unknown (HELO mailrelay1-lw-us.apache.org) (10.10.3.159) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 24 Jul 2019 23:29:25 +0000 Received: from mail-io1-f50.google.com (mail-io1-f50.google.com [209.85.166.50]) by mailrelay1-lw-us.apache.org (ASF Mail Server at mailrelay1-lw-us.apache.org) with ESMTPSA id 8F99682AF for ; Wed, 24 Jul 2019 23:29:25 +0000 (UTC) Received: by mail-io1-f50.google.com with SMTP id g20so93246741ioc.12 for ; Wed, 24 Jul 2019 16:29:25 -0700 (PDT) X-Gm-Message-State: APjAAAXD8FrIvzT8RX4N6Wlcq8Mupv2NaI2K7/ILhJiOKWwfRigT1ai/ frbdEJoT4VH/cqXcwjkvP5l3cZ7u4HA8DOb84DwBRA== X-Google-Smtp-Source: APXvYqzpuFqQ8tUZTRnxOMqXNelfeVUiDEQh6LSlG0bHFaKa2qu+D6flvucA4dyEzLbMCqBRupe6X+2YFN3ureHKvYA= X-Received: by 2002:a5e:9404:: with SMTP id q4mr17403853ioj.46.1564010964990; Wed, 24 Jul 2019 16:29:24 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Denis Magda Date: Wed, 24 Jul 2019 16:29:49 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Ignite 2.7.0 : server node: null pointer exception To: user@ignite.apache.org, dev , Ivan Rakov Content-Type: multipart/alternative; boundary="000000000000fe6d5b058e75ad0b" --000000000000fe6d5b058e75ad0b Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Igor, thanks for looking into this. Even if the root cause is on an application end, our code mustn't generate an NPE. Ignite dev community and *Ivan Rakov* in particular, have you seen this before? Should we file a ticket or the issue has already been resolved? - Denis On Wed, Jul 24, 2019 at 7:19 AM =D0=98=D0=B3=D0=BE=D1=80=D1=8C =D0=91=D0=B5= =D0=BB=D1=8F=D0=BA=D0=BE=D0=B2 wrote: > Hi, > > According to the logs I see that you've an issue with JVM pauses and node= s > disconnection, seems like it is a cause of the problem. Are you able to > reproduce this issue? > Also log contains data only for the last 15 seconds and for 1 node, could > you please provide full logs from all nodes in the cluster for futher > investigation? > > Regards, > Igor > > On Tue, Jul 23, 2019 at 6:02 PM Mahesh Renduchintala < > mahesh.renduchintala@aline-consulting.com> wrote: > >> Hi, >> >> >> We are seeing a null pointer exception in Ignite server node. >> >> >> java.lang.NullPointerException >> at >> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.la= tch.ExchangeLatchManager.canSkipJoiningNodes(ExchangeLatchManager.java:327) >> at >> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.Gr= idDhtPartitionsExchangeFuture.distributedExchange(GridDhtPartitionsExchange= Future.java:1401) >> at >> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.Gr= idDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:806= ) >> at >> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeMa= nager$ExchangeWorker.body0(GridCachePartitionExchangeManager.java:2667) >> at >> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeMa= nager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:2539) >> at >> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:12= 0) >> at java.lang.Thread.run(Thread.java:745) >> >> Please see attached. >> >> >> >> >> is there a known bug around this? >> >> >> regards >> >> Mahesh >> > --000000000000fe6d5b058e75ad0b Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Igor, thanks for looking into this.=C2=A0

Even if the root cause is on an application end, our code mustn't ge= nerate an NPE.

Ignite dev community and Ivan Ra= kov in particular, have you seen this before? Should we file a ticket o= r the issue has already been resolved?

=
-
Denis


On Wed, Jul 2= 4, 2019 at 7:19 AM =D0=98=D0=B3=D0=BE=D1=80=D1=8C =D0=91=D0=B5=D0=BB=D1=8F= =D0=BA=D0=BE=D0=B2 <igor.be= lyakov.s@gmail.com> wrote:
Hi,

According to the logs I see that you've an iss= ue with JVM pauses and nodes disconnection, seems like it is a cause of the= problem. Are you able to reproduce this issue?=C2=A0
Also log co= ntains data only for the last 15 seconds and for 1 node, could you please p= rovide full logs from all nodes in the cluster for futher investigation?

Regards,
Igor

On Tue, Jul 23, 2019 at= 6:02 PM Mahesh Renduchintala <mahesh.renduchintala@aline-consulting= .com> wrote:

Hi,=C2=A0


We are seeing a null pointer = exception in Ignite server node.=C2=A0


java.lang.NullPointerException
at org.apache.ignite.inter= nal.processors.cache.distributed.dht.preloader.latch.ExchangeLatchManager.c= anSkipJoiningNodes(ExchangeLatchManager.java:327)
at org.apache.ignite.inter= nal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFut= ure.distributedExchange(GridDhtPartitionsExchangeFuture.java:1401)
at org.apache.ignite.inter= nal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFut= ure.init(GridDhtPartitionsExchangeFuture.java:806)
at org.apache.ignite.inter= nal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body0= (GridCachePartitionExchangeManager.java:2667)
at org.apache.ignite.inter= nal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(= GridCachePartitionExchangeManager.java:2539)
at org.apache.ignite.inter= nal.util.worker.GridWorker.run(GridWorker.java:120)
at java.lang.Thread.run(Th= read.java:745)

Please see attached.=C2=A0




is there a known bug around t= his?


regards

Mahesh

--000000000000fe6d5b058e75ad0b--