We made it! Congrats, community! Thanks, Alex for pushing the release till
the end, that was a long road ;)
I decided to record a quick video featuring top-3 changes in the release.
Those are my top-3 additions while you can have yours. Anyway, check it
out:
https://youtu.be/ewwjq8SIk-s
-
Denis
Hello!
Looks like a network timeout, probably caused by firewall between two
nodes, imparting their communication.
You can try updating to 2.9 and enabling communication via discovery.
Regards,
--
Ilya Kasnacheev
чт, 8 окт. 2020 г. в 18:17, VeenaMithare :
> Hi ,
>
> Our setup :
> Servers - 3
Hello!
Have you also tried setting IgniteConfiguration.localHost property?
Regards,
--
Ilya Kasnacheev
чт, 22 окт. 2020 г. в 20:54, Gilles :
> Hello,
>
> I'm currently moving a project from development stage to production. The
> aim is that my cluster server nodes are running on multiple virt
Hello!
Does this happen every time? If so, do you have a reproducer for the issue?
Regards,
--
Ilya Kasnacheev
пт, 23 окт. 2020 г. в 13:06, narges saleh :
> Denis -- Just checked. I do specify my services to be deployed on server
> nodes only. Why would ignite think that I am running my code
Hello!
Nothing obviously wrong but it still seems to me that you're stretching it
too far.
Maybe you need to rethink your cache entry granularity (put more stuff in
the entry to make it self-contained) or use some kind of message queue.
Regards,
--
Ilya Kasnacheev
вт, 20 окт. 2020 г. в 19:37,
Hello!
This looks like a transactional deadlock. Is this operation a part of
transaction? Are you locking keys in the same order?
Regards,
--
Ilya Kasnacheev
вс, 18 окт. 2020 г. в 09:35, Kamlesh Joshi :
> Hi Igniters,
>
>
>
> Our PROD cluster was frozen due to deadlock as per below logs. Cou
This doesn't seem to help unfortunately.
Re-examining the allocation stats, it seems the app is actually allocating
around 1.5mb per second with ignite (vs only 0.15mb per second without
ignite in the app).
I've read about past issues with IGNITE_EXCHANGE_HISTORY_SIZE causing a lot
of allocations,
The Apache Ignite Community is pleased to announce the release of
Apache Ignite 2.9.0.
Apache Ignite® is an in-memory computing platform for transactional,
analytical, and streaming workloads delivering in-memory speeds at
petabyte scale.
https://ignite.apache.org
For the full list of changes, yo
Looks like you still have the 2.8.1 version of ignite-indexing. You need to
update all your dependencies, not just ignite-core.
Regards,
Stephen
> On 23 Oct 2020, at 13:36, Mahesh Renduchintala
> wrote:
>
> Hi,
>
> Migrating from 2.8.1 to 2.9.0. We are seeing the below error with thick clien
Hi,
Migrating from 2.8.1 to 2.9.0. We are seeing the below error with thick client
Please suggest how to work around it
regards
mahesh
WARNING: Failed to resolve default logging config file:
config/java.util.logging.properties
[12:33:47]__
[12:33:47] / _/ ___/
Denis -- Just checked. I do specify my services to be deployed on server
nodes only. Why would ignite think that I am running my code on a client
node?
On Fri, Oct 23, 2020 at 3:50 AM narges saleh wrote:
> Hi Denis
> What would make an ignite node a client node? The code is invoked via an
> igni
Hi Denis
What would make an ignite node a client node? The code is invoked via an
ignite service deployed on each node and I am not setting the client mode
anywhere. The code sets the jdbc connection to local and tries to execute a
sql code on the node in some interval. By the way, I didn't know on
12 matches
Mail list logo
