Thanks, Mike!
I will update and verify it.
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi
the issue was fixed: https://issues.apache.org/jira/browse/IGNITE-11952
please check the latest version 2.8.0
Thanks,
Mike.
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Sorry for using the same topic of
http://apache-ignite-users.70518.x6.nabble.com/TcpDiscoverySpi-worker-thread-failed-with-assertion-error-td14554.html
Actually I met the same issue exactly, although it was fixed in
https://issues.apache.org/jira/browse/IGNITE-5562
We have more than 6 clusters
Hi Slava,
Thank you very much for your answer.
Juan
From: Вячеслав Коптилин [mailto:slava.kopti...@gmail.com]
Sent: Monday, July 10, 2017 12:21 PM
To: user@ignite.apache.org
Subject: Re: TcpDiscoverySpi worker thread failed with assertion error
Hi Juan,
U.currentTimeMillis(), which is based
Hi Juan,
U.currentTimeMillis(), which is based on System.currentTimeMillis(), is not
monotonic,
so there is no guarantee that returned values will always be greater than
all previous calls.
please see the following ticket:
https://issues.apache.org/jira/browse/IGNITE-5562
Thanks,
Slava.
2017-07
[mailto:juan.bar...@unitedplanet.com]
Sent: Monday, July 10, 2017 11:34 AM
To: user@ignite.apache.org<mailto:user@ignite.apache.org>
Subject: TcpDiscoverySpi worker thread failed with assertion error
Hi everyone,
We are testing a new application running Ignite 2.0 with 3 nodes running on
Azure pl
On 10.07.2017 11:44, Juan Barani wrote:
Just to add something else to the scenario, can it happen that due to
NTP adjustments in the servers then System.currentTimeMillis() returns
a smaller value than before? May it be that using System.nanoTime()
this problem does not appear?
I guess nano
...@unitedplanet.com]
Sent: Monday, July 10, 2017 11:34 AM
To: user@ignite.apache.org
Subject: TcpDiscoverySpi worker thread failed with assertion error
Hi everyone,
We are testing a new application running Ignite 2.0 with 3 nodes running on
Azure platform.
We left the cluster running a couple of
Hi everyone,
We are testing a new application running Ignite 2.0 with 3 nodes running on
Azure platform.
We left the cluster running a couple of days without load, and randomly one of
the Nodes stopped with the following stacktrace:
INFO 2017-07-07T23:07:28,475 -
org.apache.ignite.internal.Ig
