Re: Using @SpringResource & @SpringApplicationContextResource in IgniteCallable

Please help -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: ApacheCon talk available

Saikat, thanks a lot! *applause* On Fri, Oct 16, 2020 at 12:11 AM Saikat Maitra wrote: > > Hi, > > My talk about Data Streaming using Apache Flink and Apache Ignite in > ApacheCon is available now > > https://www.youtube.com/watch?v=n74HMmTz5i0 > > Regards, > Saikat

ApacheCon talk available

Hi, My talk about Data Streaming using Apache Flink and Apache Ignite in ApacheCon is available now https://www.youtube.com/watch?v=n74HMmTz5i0 Regards, Saikat

Re: 3.0 and messaging

Hi Mikael, Please check the discussion on the dev list [1] In short: - Messaging can be simulated with Services and/or Compute to some extent - Some people have the same concern as you, so it is not clear yet whether we are going to remove messaging or not [1]

Continuous query not transactional ?

Hi , This is in continuation of the below statement on this post : http://apache-ignite-users.70518.x6.nabble.com/Lag-before-records-are-visible-after-transaction-commit-tp33787p33861.html >>Continuous Query itself is not transactional and it looks like it can't be used for this at the moment.

Re: Lag before records are visible after transaction commit

Hi , >>Continuous Query itself is not transactional and it looks like it can't be used for this at the moment. So, it gets notification before other entries were committed. Does this mean we could get dirty reads as updates in continuous query ? i.e. for eg if the code is as below: 1. Start

3.0 and messaging

Hi! It sounds like the messaging API will be removed from 3.0, is that correct ? I use the messaging a lot so in that case I guess I have to work out some other solution for sending messages between nodes, any idea on the best solution for this ?

Re: Different cache expiry policy each node..

Hello! You can also use cache.withExpiryPolicy() to adjust that on the fly since it's really a property of data. Regards, -- Ilya Kasnacheev ср, 14 окт. 2020 г. в 05:19, kay : > Hello, I have 4 server nodes. > > and each node have a cache with 4minutes Modified expirypolicy.. > > I restarted

Re: Ignite instance fails. Unsure as to root cause

Hello! Oct 12 17:49:41 nalrcsvridbq02 kernel: watchdog: BUG: soft lockup - CPU#0 stuck for 38s! [kworker/u256:0:3703404] This is bad. Your system kernel says your CPU#0 was hanging for 38 seconds. This is enough to trigger failure detection timeout and kill and instance, or at least for the

Re: java.lang.IllegalStateException: Getting affinity for too old topology version that is already out of history

Hello! Why not, if it fixes the issue for you. Then you can try 2.9.0 once it is out. Unfortunately, a small snippet of server log is not sufficient, complete log is needed. I can already spot some communication problems, though. Regards, -- Ilya Kasnacheev чт, 15 окт. 2020 г. в 09:50, swara

Re: java.lang.IllegalStateException: Getting affinity for too old topology version that is already out of history

Hello We are using this type of cache design from last 3 years with 2.5.6 version. we never got any issue. When we upgraded to 2.8.1 we are getting this type of errors. Should we downgrade to 2.8.0 or 2.5.6. Please suggest? Thank You Swara -- Sent from: