: user@ignite.apache.org
Subject: Re: How to correctly shut down Ignite Application
Hi Juan,
Looks like there is a bug, sometimes ignite choose ipv6 protocol to communicate
with other nodes that causes strange communication errors.
On Wed, May 10, 2017 at 1:01 PM, Juan Barani
mailto:juan.bar
~[ignite-core-2.0.0.jar:2.0.0]
>
> at
> org.apache.ignite.internal.util.IgniteUtils$18.run(IgniteUtils.java:1884)
> ~[ignite-core-2.0.0.jar:2.0.0]
>
> ... 5 more
>
>
>
> These errors disappeared after setting: -Djava.net.preferIPv4Stack=tru
pv6, but cannot tell why the NPE was coming.
Probably the errors are related.
Thanks!
Juan
From: Andrey Mashenkov [mailto:andrey.mashen...@gmail.com]
Sent: Tuesday, May 9, 2017 7:49 PM
To: user@ignite.apache.org
Subject: Re: How to correctly shut down Ignite Application
Looks like client node ca
Looks like client node can't connect to server
[id=2b404f04-cad5-4209-a615-ab3b9639b8e4, addrs=[0:0:0:0:0:0:0:1%1,
127.0.0.1, 172.30.32.89].. *isClient=false*]
Would you please attach full logs?
On Tue, May 9, 2017 at 2:55 AM, baozipu wrote:
> Hi,
>
> Thanks for the reply. Both the applications
Hi,
Thanks for the reply. Both the applications are launched in Embedded mode in
Spark. I am not sure if the flag of preferIPv4Stack still matters.
Both of the applications runs perfect when they are alive. It is only when
the "client application" (actually another application in server mode)
clo
Hi,
Try to set same option for all nodes either -Djava.net.preferIPv4Stack=true
or -Djava.net.preferIPv6Stack=true.
There is an example in ignite.sh.
On Tue, May 9, 2017 at 12:19 AM, baozipu wrote:
> Hello, here is my topology configuration:
>
> 1. One Ignite server application, which holds som
