Re: Failed to start near cache (a cache with the same name without near cache is already started)

Hi! You need to be careful, with copyOnRead disabled, any local read can return a "real" copy of the object and you can cause pretty weird bugs if you modify that object, so be careful with that or best is to only use it for readonly cases. If you see that much performance improvement I woul

Re: Failed to start near cache (a cache with the same name without near cache is already started)

I have disabled copyonread and the time taken to getAll() reduced to 1/3. Earlier it was 300 ms on 10k entries and now it is 100ms. Is disabling copyonread is fine ??? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Failed to start near cache (a cache with the same name without near cache is already started)

Hello! Did you try to profile it? What is taking the time? Regards, -- Ilya Kasnacheev ср, 27 нояб. 2019 г. в 18:59, Hemambara : > Thank you. I am not getting this error now. But not sure if something wrong > with config. When I call getAll(all keys) on near cache, then the > performance is w

Re: Failed to start near cache (a cache with the same name without near cache is already started)

Thank you. I am not getting this error now. But not sure if something wrong with config. When I call getAll(all keys) on near cache, then the performance is worse than regular cache. If regular cache getAll() is taking 100ms then near cache getAll() is taking 330 ms. Its almost 3 times. I am expect

Re: Failed to start near cache (a cache with the same name without near cache is already started)

This happens because you created a cache without a near configuration first then tried to create it again with a near config. for example: start a server node then do as follows: NearCacheConfiguration nearCfg = new NearCacheConfiguration<>(); IgniteCache cache1 = ignite.getO

Failed to start near cache (a cache with the same name without near cache is already started)

I followed the below post http://apache-ignite-users.70518.x6.nabble.com/Failed-to-start-near-cache-a-cache-with-the-same-name-without-near-cache-is-already-started-td18322.html but it did not solve my problem, hence requesting for help. I tried two options a) Start ignite with below xml config

Re: Failed to start near cache (a cache with the same name without near cache is already started

Hi, Near caches are transparent for you - there is no user API to get reference to or work with near caches. The purpose of a near cache is to "cache the cache", that is to be a local cache for a distributed cache. Ignite transparently fills near cache with the most recent data when you work with

Re: Failed to start near cache (a cache with the same name without near cache is already started

Hi Alex, Thank you for your reply. But I am not quite clear about how to create near cache for TableA and TableB? Thanks, Sherry -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Failed to start near cache (a cache with the same name without near cache is already started

Hi, Near caches are configured per cache and not per query. You cannot start different near caches for the same distributed cache. Start separate near caches for TableA and TableB.

Failed to start near cache (a cache with the same name without near cache is already started

query(sql).getAll()... " And if I run the second method, it will show error logs like "javax.cache.CacheException: class org.apache.ignite.IgniteCheckedException: Failed to start near cache (a cache with the same name without near cache is already started)" And also everytime if i run cross caches queries,