Re: Lost partitions automatically reset

akorensh wrote > The issue you described is a bit different from the original topic. >This one deals with incorrect lostPartitions() count Sorry about that. As I mentioned I have two different behaviors, hence the mess up. I am trying to reproduce the original issue, the one I am experiencin

Re: Lost partitions automatically reset

I have two different scenarios or behaviors, none is working as I would expect. One is what I am experiencing in my project (whole project) and the other one is what I am experiencing when creating a toy project trying to reproduce it. In both cases, I am using Ignite 2.7.6. This is the code I am

Re: Lost partitions automatically reset

Hi, The partition loss policy is READ_WRITE_SAFE. I know because: - I am subscribed to the EVT_CACHE_REBALANCE_PART_DATA_LOST, which is being called for each lost partition. - I am calling cache.lostPartitions(), which returns the array with all the lost partitions. This call is done

Lost partitions automatically reset

Hello I have a cluster with 3 nodes with persistence enabled. I have a distributed cache with backup = 1 where I put some data. After I shutdown NODE-2 and NODE-3 some partitions state become LOST. Then I run NODE-2 again, all the data from the cache is enabled again, but the partition loss polic

Re: Use custom Data Region or custom Cache for IgniteAtomicReference - Ignite 2.3

Hello, I will set the defatulDataRegion as persistent. Thank you very much for your help Iliya! Regards. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Use custom Data Region or custom Cache for IgniteAtomicReference - Ignite 2.3

Hello, I am using 2.7.6 in the code I shared. I didn't want to open a new post and continued a thread with "Ignite 2.3" in the title . Regards, -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Use custom Data Region or custom Cache for IgniteAtomicReference - Ignite 2.3

Hi, I uploaded the code I am using to this repo. Github:IgnitePlayground It is coded in Kotlin. I run multiple nodes by running NodeStartup and then I run Client, which triggers the AtomicSequence increase. Thanks, -- Sent from: http://apa

Re: Use custom Data Region or custom Cache for IgniteAtomicReference - Ignite 2.3

Hi Ilya, I perform a single test: - I run 3 nodes - Create an AtomicSequence (Default AtomicConfiguration). - getAndIncrement a few times in each node. - One uses 0, 1, ... - Other node uses 1000, 1001, ... - ... - Shut down all the nodes. - Run all the nodes again. - Creat

Re: User-defined event

It was my fault. I was not listening to remote events. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Use custom Data Region or custom Cache for IgniteAtomicReference - Ignite 2.3

Hello, Thanks a lot, Ilya. According to this snippet, It should work when a DefaultDataRegion is configured, as you mention. I have tested and checked that this function returns true but it doesn't work, the AtomicSequence I am expecting to be persistent is not persisted. >From my point of view,

Re: Use custom Data Region or custom Cache for IgniteAtomicReference - Ignite 2.3

Hi, Ilya, I am afraid I have tested it and it doesn't. Thanks! ilya.kasnacheev wrote > Hello! > > I think that system region is persistent if *any* of the regions is > persistent, not just the default one. > > Regards, > -- > Ilya Kasnacheev -- Sent from: http://apache-ignite-users.7051

User-defined event

Hi, I am running Ignite 2.7.0. I am trying to trigger a user-defined event that can be listened by all the nodes in the cluster but in the IgniteEvents API there is just 'recordLocal', which doesn't trigger the listeners in remote nodes. I have looked for a way of doing so in the documentation bu

Re: Use custom Data Region or custom Cache for IgniteAtomicReference - Ignite 2.3

I am using Ignite 2.7.0 -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Use custom Data Region or custom Cache for IgniteAtomicReference - Ignite 2.3

Hi, I need to store the ignite-sys-atomic-cache in a persistent region, but I don't want to set the default region to persistent since I am not sure of what it implies. The AtomicConfiguration allows you to set the group name, but it crashes if you set a group name that has any cache in a persist

Re: "Failed to deserialize object" in Client Mode

Yes. The thing is that when I run the node (same configuration and same version) just switching to server mode it works properly. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

"Failed to deserialize object" in Client Mode

Hello, I am trying to modify the baseline topology by using setBaselineTopology . When I run it from a Server Node it works but when I run it form a Cient node I am