Re: Failed to execute the cache operation (all partition owners are left the grid partition data has been lost))

Seems you faced with https://issues.apache.org/jira/browse/IGNITE-14073   >Hi, >I have .Net Ignite client and server app Ignite v2.9.1. we have a 2 node >cluster, >recently we are upgraded ignite 2.7.6 to ignite 2.9.1 after using this >version we are facing issues frequently. >

Re: Ignite Startup Warnings

Thanks for your replies and creating the issue. ilya.kasnacheev wrote > The second one is clearly also a bug. You can sidestep it by setting log > level to INFO. Shall I create an issue for the second one too? Regards, Paolo -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Failed to execute the cache operation (all partition owners are left the grid partition data has been lost))

Hi, I have .Net Ignite client and server app Ignite v2.9.1. we have a 2 node cluster, recently we are upgraded ignite 2.7.6 to ignite 2.9.1 after using this version we are facing issues frequently. [req=o.a.i.i.processors.platform.client.cache.ClientCacheGetRequest@bb5fb96]

Re: 2.8.1 : Continuous Query Initial query not returning any result sometimes and UnregisteredBinaryTypeExceptio

On further debugging, it looks like all the clients that had failed the count, were executing their query on the same server machinename002. When I looked at the server logs, it looks like that the records that were missing were not present on this server when the query was executed but were

ignite common code gitflow

Hi, guys! I am implementing an Ignite cluster with data node, service node and spring boot node (REST API) with embedded ignite client. My nodes have common POJO classes. Is there a nice approach to store all nodes at single repository (sharing common POJO) to implement common unit testing for