[GridCacheMapEntry] Failed to update counter for atomic cache

Hi Team, I got below exception on my ignite server node. Would you please help me to check why I am getting this exception? [19:33:25,235][SEVERE][sys-stripe-1-#2][GridCacheMapEntry] Failed to update counter for atomic cache [, initial=false, primaryCntr=null, part=GridDhtLocalPartition [id=425,

[Ignite Summit] Keynote Speakers and how can you influence the future schedule of the event

Hi Igniters! The CFP is closed, and our Program Committee members are working hard on submission evaluation. You can check accepted keynotes on the website: https://ignite-summit.org/schedule The future of elastic databases - Dmitriy Setrakyan, Apache Ignite PMC, Sr. Manager at AWS Aurora

Get always return null in java thick client for data inserted in python thin client

Hello, I am trying to read some data on my java client nodes that has been inserted on the server nodes by a python thin client. The cache is a key-value for types int-HashSet. I can insert the data flawlessly in python, I can read the data in the java client using a ScanQuery, using an

Client node disconnected from cluster

Getting below error on ignite server: FAIL: [tcp-disco-client-message-worker-[[CredentialsTcpDiscoverySpi] Client node considered as unreachable and will be dropped from cluster, because no metrics update messages received in interval: TcpDiscoverySpi.clientFailureDetectionTimeout() ms. It may be

Re: JMX Exporters with Ignite

Hello! It will always add this number by default. You need to restart all nodes with this setting to get rid of it. Regards, -- Ilya Kasnacheev ср, 5 мая 2021 г. в 14:31, Naveen : > Thanks Ilya, it works and resolve my issue to an extent, but need to > restart > all the nodes to get this