Re: Ignite.Net Server & client node

Hi, Every request is communicated to the server, there is no "local cache" or anything like that. On Fri, Nov 8, 2019 at 8:37 PM Sudhir Patil wrote: > Hi All, > > In ignite.net server node stores cache data and a thin client > communicates with server to get cache data. > > In such situations,

Ignite.Net Server & client node

Hi All, In ignite.net server node stores cache data and a thin client communicates with server to get cache data. In such situations, post 1 request of cache data by thin client, does all further requests still communicate with server or it stores that cache data on thin client and server from

tcp-comm-worker-#1 attempt to connect to unrecognized IP addresses

I am running a 4 node ignite cluster in AWS. We are running ignite inside of Docker containers (the image is apacheignite/ignite:2.7.6 from Dockerhub). The container is setup to use the host network. I noticed a lot of warning from the tcp-comm-worker-#1 thread in which it is attempting to

Re: Cluster in AWS can not have more than 100 nodes?

Hi Ilya yes from the message I can see there are more than 100 server nodes : Topology snapshot [ver=2104, locNode=63120c8d, servers=117, clients=129, state=ACTIVE, CPUs=9240, offheap=2300.0GB, heap=7300.0GB] We are running a spark job keep writing to the database every minute. At least from

Re: How to insert data?

Hi Boris, Perhaps confusing point here is that Ignite separates key and value parts in KV storage. And there is always underlying KV storage in Ignite. So you cannot have cache key and value in a single POJO. I tried your class with annotations and run INSERTs with it. A trick here is a "_key"

Re: Blocked Worker Thread

Hi Conrad, The reasons can be different. Could you please share the logs? BR, Andrei 11/7/2019 10:35 PM, Conrad Mukai (cmukai) пишет: We are running a cache in a 4 node cluster with atomicityMode set to ATOMIC and have persistence enabled. We repeatedly get a SYSTEM_WORKER_BLOCKED error on

Re: recoveryBallotBoxes in MvccProcessorImpl memory leak?

Hello! This is very strange, since we expect this collection to be cleared on exchange. Please make sure you don't have any stray exceptions during exchange in your logs. Regards, -- Ilya Kasnacheev пт, 8 нояб. 2019 г. в 12:49, mvkarp : > Hi, > > This is not the case. Always only a maximum

Re: recoveryBallotBoxes in MvccProcessorImpl memory leak?

Hi, This is not the case. Always only a maximum total of two server nodes. One JVM server on each. However there are many client JVMs that start and stop caches with setClientMode=true. It looks like one of the server instances is immune to the issue, whilst the most newly created one gets the

Re: Ignite-spring-data_2.0 not working

Thanks, is there a way to use IgnoreCase as well? IgnoreCase findByFirstnameIgnoreCase … where UPPER(x.firstame) = UPPER(?1) https://docs.spring.io/spring-data/jpa/docs/1.5.1.RELEASE/reference/html/jpa.repositories.html#jpa.query-methods.query-creation Or another way to do

Re: Ignite-spring-data_2.0 not working

Hello! I don't recommend this since index can't be use in this case. Better introduce firstNameInUpper field. Regards, -- Ilya Kasnacheev пт, 8 нояб. 2019 г. в 18:32, Humphrey : > Thanks, is there a way to use IgnoreCase as well? > > IgnoreCase findByFirstnameIgnoreCase … where

Re: recoveryBallotBoxes in MvccProcessorImpl memory leak?

Ok, there are no exceptions in the ignite logs for the client JVMs but I've attached the log for one of the problem servers. Looks like a few errors but I am unable to determine the root cause. ignite-46073e05.zip

Re: Ignite-spring-data_2.0 not working

Thanks, I've tried it with version 2.0.14 and it works, but version 2.1.0 it doesn't. org.springframework.data spring-data-commons 2.0.14.RELEASE Humphrey -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite-spring-data_2.0 not working

Hello! Well, I guess that's how it is currently. Regards, -- Ilya Kasnacheev пт, 8 нояб. 2019 г. в 17:17, Humphrey : > Thanks, > > I've tried it with version 2.0.14 and it works, but version 2.1.0 it > doesn't. > > > org.springframework.data > spring-data-commons > 2.0.14.RELEASE > >

Re: recoveryBallotBoxes in MvccProcessorImpl memory leak?

Hello! You seem to have an awful lot of errors related to connectivity problems between nodes, such as: Suppressed: class org.apache.ignite.IgniteCheckedException: Failed to connect to address [addr=ult-s2-svr1.dataprocessors.com.au/10.16.1.47:47106, err=Connection refused] Suppressed: class