Near Cache

Hello Igite List, Do near caches ( https://ignite.apache.org/docs/latest/configuring-caches/near-cache) store entries in binary or object form? We have a use case where we'd like to avoid the cost of deserialization when reading from a frequently accessed (and infrequently updated) cache. T

Re: Near Cache Updates on Thick clients

Yes, near caches are updated/invalidated automatically, you don't have to worry about stale data. On Sat, Oct 16, 2021 at 7:15 AM wrote: > Can someone please confirm the behavior of near caches? Do they get > updated automatically when the cache on cluster server node get updated? > > >

Near Cache Updates on Thick clients

Can someone please confirm the behavior of near caches? Do they get updated automatically when the cache on cluster server node get updated?

Re: Verification of near cache works

Hi, you can try IgniteCache#localPeek(CachePeekMode.NEAR), localSize(CachePeekMode.NEAR), and localEntries(CachePeekMode.NEAR) to check the data in the near cache. On Thu, Oct 14, 2021 at 10:49 AM Aliaksandr Kazlou < aliaksandr.kaz...@gmail.com> wrote: > Hi, guys. What is the best way

Verification of near cache works

Hi, guys. What is the best way to verify near caching works? So far Visor shows 0 hit on it. What if SQL is used on top of the caches where near-cache is configured, will SQL takes into account this, or SQL query always has to run on remote, and never on local/near cache data? Overall we have

Re: Near Cache versus Continuous Query

Hello! 1. I'm not sure, but perhaps this is due to necessity to track nodes with near cache to keep it in sync. 2. I'm not sure there's the best way. Near cache is a cache, and "cache" usually means "hot subset". The only way to be sure about complete in-sync

Re: Near Cache versus Continuous Query

I have 3 questions: 1. Why do the server nodes use on heap storage when a client initializes a dynamic near cache? We have never noticed any on-heap storage usage before using a near cache on one of our clients. Observe no caches initialized on server Initialize a normal cache

Re: Near Cache versus Continuous Query

= > I tried using a NearCache on the webserver thick clients but this had two > undesireable problems: > * it created a near cache on each server node which I have no use for since > this is already an replicated cache > * the near cache never received new entries from the replicated c

Re: Near Cache versus Continuous Query

Hi, > it created a near cache on each server node There are two Near Cache modes: * Server Node Near Cache - configured once before cache start for all server nodes * Client Node Near Cache - configured dynamically on per-node basis Please make sure to use the second mode, like explained

Near Cache versus Continuous Query

copy of that cache. NearCache Attempt: = I tried using a NearCache on the webserver thick clients but this had two undesireable problems: * it created a near cache on each server node which I have no use for since this is already an replicated cache * the near cache never received new

Near Cache versus Continuous Query

copy of that cache. NearCache Attempt: = I tried using a NearCache on the webserver thick clients but this had two undesireable problems: * it created a near cache on each server node which I have no use for since this is already an replicated cache * the near cache never received new

Re: Best way to find MAX value of field in Near cache

What it means is that the near cache isn’t used when you execute the SQL query. A subtle but important difference! > On 29 Sep 2020, at 15:15, njcstreet wrote: > > Hi, > > Sorry yes you are right - it does seem to work. I had seen the post below: > > http://apache-

Re: Best way to find MAX value of field in Near cache

Hi, Sorry yes you are right - it does seem to work. I had seen the post below: http://apache-ignite-users.70518.x6.nabble.com/How-sql-works-for-near-cache-td30518.html Where the answer says “ SQL doesn't work with near caches at all” but I guess this is wrong. Thanks! -- Sent from:

Re: Best way to find MAX value of field in Near cache

How are you creating your cache? You can absolutely use SQL with a cache that has a near cache. > On 29 Sep 2020, at 09:16, njcstreet wrote: > > Hi, > > I have a replicated cache that is fronted by a near cache in my client (data > loader) application. In this cache I hav

Best way to find MAX value of field in Near cache

Hi, I have a replicated cache that is fronted by a near cache in my client (data loader) application. In this cache I have an integer field which is used as a lookup key into the cache. I am using IgniteAtomicSequence to generate this lookup key (since I believe there is no such thing as an auto

Re: How to get local node near cache metrics?

Hello! The only thing I can think of is cache.metrics().getHeapEntriesCount() Have you tried that? Regards, -- Ilya Kasnacheev вт, 14 июл. 2020 г. в 05:12, John Smith : > Hi I want to get how many entries are on the thick client's near cache. Is > there a way? >

How to get local node near cache metrics?

Hi I want to get how many entries are on the thick client's near cache. Is there a way?

Re: Near Cache Support For Thin Clients

the >> events of when cache items within the cluster are added, modified, or >> deleted. >> >> On Thu, May 21, 2020 at 2:29 PM Marty Jones >> wrote: >> >>> Honestly near cache for the thin client is a must for me. Implementing >>> this is a h

Re: Near Cache Support For Thin Clients

ion of the nearcache if I can get the > events of when cache items within the cluster are added, modified, or > deleted. > > On Thu, May 21, 2020 at 2:29 PM Marty Jones wrote: > >> Honestly near cache for the thin client is a must for me. Implementing >> this is a huge pe

Re: Near Cache Support For Thin Clients

Has there been a request for event listeners for the thin clients? I am happy to roll my own implementation of the nearcache if I can get the events of when cache items within the cluster are added, modified, or deleted. On Thu, May 21, 2020 at 2:29 PM Marty Jones wrote: > Honestly near ca

Re: Near Cache Support For Thin Clients

Honestly near cache for the thin client is a must for me. Implementing this is a huge performance gain. On Thu, May 21, 2020 at 5:47 AM Pavel Tupitsyn wrote: > Alex, > > I've recently implemented .NET Native Near Cache [1]. > It is a very similar concept, because cachin

Re: Near Cache Support For Thin Clients

Alex, I've recently implemented .NET Native Near Cache [1]. It is a very similar concept, because caching is performed on platform side. We had requests for this from different users for quite some time. Users were implementing this on their own with Continuous Queries. Yes, it i

Re: Near Cache Support For Thin Clients

Hello, I don't think that near cache for thin client on Ignite level it's a good idea. Expiration is not the only case here. For thick clients near caches are transactionally consistent. For thin clients such a guarantee never can be provided. Near cache for thin clients will be either

Re: Near Cache Support For Thin Clients

20 at 2:52 PM Marty Jones wrote: > The use case is having a local cache that stores most widely used cache > items in memory on server instead of having the network expense of pulling > them down every time they are requested. The main thing is the near cache > has to support removing

Re: Near Cache Support For Thin Clients

The use case is having a local cache that stores most widely used cache items in memory on server instead of having the network expense of pulling them down every time they are requested. The main thing is the near cache has to support removing cache items that have expired on the server. The

Re: Near Cache Support For Thin Clients

Can you please describe the use case in more detail? What do you expect from such a feature? On Tue, May 19, 2020 at 2:01 AM martybjo...@gmail.com wrote: > I wanted to see if there are any plans to support near caches for thin > clients? I think it would be a great feature. I know I could use it

Near Cache Support For Thin Clients

I wanted to see if there are any plans to support near caches for thin clients? I think it would be a great feature. I know I could use it right now. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Near cache configuration for partitioned cache

Dominik, This cache was already created in the cluster with Near Cace for all nodes. Once created, this configuration can't be changed, so, it's needed to clean persistence data or just destroy the cache and create it without Near Cache in configuration. After this, you can dynamicall

Re: Near cache configuration for partitioned cache

Hi, between first test with near cache configured in xml and configuring near cache via java code i cleaned data. But why should I clean data on server nodes when I add near cache only on client nodes to gain performance? Now I am testing ignite so I could do this, but it won't be acceptable

Re: Near cache configuration for partitioned cache

gt; > +-------+ > > 1st and 2nd entries are clients and 3rd and 4th are server nodes. > My client nodes has LRU near cache with size 10 and I am querying > c

Re: Near cache configuration for partitioned cache

| +---+ 1st and 2nd entries are clients and 3rd and 4th are server nodes. My client nodes has LRU near cache with size 10 and I am querying cache with 15 random data. But why there are heap entries on server nodes? wt., 24 mar 2020 o 08:40 Dominik Przybysz napisał(a

Re: Near cache configuration for partitioned cache

Hi, exactly I want to have near cache only on client nodes. I will check your advice with dynamic cache. I have two server nodes which keep data and I want to get data from them via my client nodes. I am also curious what had happened with heap on server nodes. pon., 23 mar 2020 o 23:13 Evgenii

Re: Near cache configuration for partitioned cache

Hi, Near Cache configuration in xml creates near caches for all nodes, including server nodes. As far as I understand, you want to have them on client side only, right? If so, I'd recommend to create them dynamically: https://www.gridgain.com/docs/latest/developers-guide/near-cache#creating

Near cache configuration for partitioned cache

I loaded 1,5mln entries into cluster via data streamer. I tested this topology without near cache and everything was fine, but when I tried to add near cache to my client nodes then server nodes started to keep data on heap and reads rps dramatically fell down (150k

Re: Possible memory leak when using a near cache in Ignite.NET?

;> application that writes into the caches. >>> >>> The caches are PARTITIONED and TRANSACTIONAL and the partitions have two >>> backups. >>> >>> It's been working fine so far but we identified that one particular >>> cache was the most rea

Re: Possible memory leak when using a near cache in Ignite.NET?

titions have two >> backups. >> >> It's been working fine so far but we identified that one particular cache >> was the most read and to reduce network usage and improve response time of >> the gRPC service we decided to use a near cache. That particular cache has &

Re: Possible memory leak when using a near cache in Ignite.NET?

IONED and TRANSACTIONAL and the partitions have two > backups. > > It's been working fine so far but we identified that one particular cache > was the most read and to reduce network usage and improve response time of > the gRPC service we decided to use a near cache. That particula

Possible memory leak when using a near cache in Ignite.NET?

and TRANSACTIONAL and the partitions have two backups. It's been working fine so far but we identified that one particular cache was the most read and to reduce network usage and improve response time of the gRPC service we decided to use a near cache. That particular cache has ~2300 entries

Re: How sql works for near cache

Hemambara wrote: > Is there any way we can get complete keyset or values from a near cache. > Something like cache.keyset() > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >

Re: How sql works for near cache

Hello! You can use cache.localEntries(CachePeekMode.NEAR); Regards, -- Ilya Kasnacheev ср, 4 дек. 2019 г. в 02:36, Hemambara : > Is there any way we can get complete keyset or values from a near cache. > Something like cache.keyset() > > > > -- > Sent from: http://apac

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 > perfo

Re: How sql works for near cache

Is there any way we can get complete keyset or values from a near cache. Something like cache.keyset() -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: How sql works for near cache

Hi, Near cache makes sense only for key-value access, SQL doesn't work with near caches at all. Evgenii вт, 3 дек. 2019 г. в 04:20, Hemambara : > If I run sql with out where condition on near caches, query will hit server > node correct ? It wont fetch from near cache in local node

How sql works for near cache

If I run sql with out where condition on near caches, query will hit server node correct ? It wont fetch from near cache in local node. Is this a true statement? Ex: select _key from cachename; -- 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)

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

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

cache1 = ignite.getOrCreateCache("myCache1"); IgniteCache cache2 = ignite.getOrCreateNearCache("myCache1", nearCfg); <-- exception thrown here because you already created this cache In order to remedy this put the near cache config into the original cache config. i.e.

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: Benefits of near cache other than get() ?

Hi, In case near cache contains requested data it will be used for read operations, such as get() and getAll(). If all the data from the cache doesn't fit into Near cache, then eviction will be applied and existing records in the cache will be replaced by the records from the remote

Benefits of near cache other than get() ?

What are the operations, out of below, that are purely benefited by near cache. When I tested it other than get() I do not see any benefit of near cache. All the other calls are going on network. I thought getAll(), keySet() and entrySet() will be coming from local node, but they are going to

Re: [cpp] Setup a near cache on client and server nodes

nk, it is not possible right now from pure C++. > > Best Regards, > Igor > > > On Sat, Sep 14, 2019 at 1:02 AM Denis Magda wrote: > >> Igor, >> >> Any idea how to start a cache dynamically from C++ thick client passing >> near cache settings? >> &

Re: [cpp] Setup a near cache on client and server nodes

Denis, No ideas here. I think, it is not possible right now from pure C++. Best Regards, Igor On Sat, Sep 14, 2019 at 1:02 AM Denis Magda wrote: > Igor, > > Any idea how to start a cache dynamically from C++ thick client passing > near cache settings? > > Don't se

Re: [cpp] Setup a near cache on client and server nodes

Igor, Any idea how to start a cache dynamically from C++ thick client passing near cache settings? Don't see how we can do it know unless you start a special Java app that starts the caches with required settings and dies. - Denis On Fri, Sep 13, 2019 at 2:34 PM Oleg Popov wrote: &

Re: [cpp] Setup a near cache on client and server nodes

As I wrote before - I create caches dynamically and cannot declare cache configuration in client.xml because cache doesn't exist yet. From: "Denis Magda" To: "user" Sent: Friday, September 13, 2019 10:50:16 PM Subject: Re: [cpp] Setup a near cache on client and

Re: [cpp] Setup a near cache on client and server nodes

Oleg, You need to add the near cache settings to Ignite client configuration explicitly. Please try out the code snippets from this documentation page: https://apacheignite.readme.io/docs/near-caches - Denis On Fri, Sep 13, 2019 at 12:36 PM Oleg Popov wrote: > I use thick client. I do

Re: [cpp] Setup a near cache on client and server nodes

I use thick client. I don't have any records with caches configurations in my client XML file (I create caches dynamically through REST requests and caches templates). I don't know where I should place a near cache configuration on a client. Should I explicitly declare a cache con

Re: [cpp] Setup a near cache on client and server nodes

REST/caches templates. > > Need: > > 1. C1 has to have a near cache for better performance. > > Question: > > 1. How to enable and use a near cache on client and data nodes ? > 2. Is there any support NearConfiguration in C++ ? > > I have already tried

[cpp] Setup a near cache on client and server nodes

Hello. Configuration: 1. N1 и N2 - data nodes (in different k8s clusters). 2. C1 - client node (outside of k8s clusters; c++ client node). 3. All caches are replicated. Caches create through REST/caches templates. Need: 1. C1 has to have a near cache for better performance. Question

Re: Ignite ignores cache config when putting entries through near cache

. BR, Andrei 9/6/2019 12:36 PM, Bartłomiej Stefański пишет: Hi, I have a problem with putting entries to partitioned or replicated cache through near cache on client node. Even when I configured cache on server to put values to off-heap space they are stored on heap. I already descibed it o

Ignite ignores cache config when putting entries through near cache

Hi, I have a problem with putting entries to partitioned or replicated cache through near cache on client node. Even when I configured cache on server to put values to off-heap space they are stored on heap. I already descibed it on jira https://issues.apache.org/jira/projects/IGNITE/issues

Re: Issue in starting Near cache only on client node

Hello! Unfortunately, near caches configuration is somewhat confusing. I can see in the docs the following: // Create a distributed cache on server nodes and // a near cache on the local node, named "myCache".IgniteCache cache = ignite.getOrCreateCache( new CacheConfiguratio

Re: Issue in starting Near cache only on client node

Actually I wanted to start near cache only on client node using getOrCreateNearCache method. But somehow it didn't work. So now. I have configured near cache using cache.setNearCacheConfig method in cache configuration. But this starts near cache on client as well as on server node. On

Re: Issue in starting Near cache only on client node

es. > > *class org.apache.ignite.IgniteCheckedException: Failed to start near > cache (a cache with the same name without near cache is already started* > > To solve this issue I added following code in ApplicationRunner's run() > method to explicitly start the cache. Application run

Re: Issue in starting Near cache only on client node

Can some please advise? On Thu, Jun 27, 2019 at 1:01 PM Prasad Bhalerao < prasadbhalerao1...@gmail.com> wrote: > Hi, > > I am getting following error on ignite client nodes. > > *class org.apache.ignite.IgniteCheckedException: Failed to start near > cache (a cache with th

Re: Issue in starting Near cache only on client node

Hi, I am getting following error on ignite client nodes. *class org.apache.ignite.IgniteCheckedException: Failed to start near cache (a cache with the same name without near cache is already started* To solve this issue I added following code in ApplicationRunner's run() method to expli

Re: Which cache gets expiry policy when creating near cache?

;> Regards, >>> -- >>> Ilya Kasnacheev >>> >>> >>> чт, 23 мая 2019 г. в 17:53, John Smith : >>> >>>> So then I should create my regular cache first... Set the expiry policy >>>> on that and then create near cache on top

Re: Which cache gets expiry policy when creating near cache?

at 11:27, Ilya Kasnacheev > wrote: > >> Hello! >> >> Yes, I guess so. >> >> Regards, >> -- >> Ilya Kasnacheev >> >> >> чт, 23 мая 2019 г. в 17:53, John Smith : >> >>> So then I should create my regular cache first... Set the

Re: Which cache gets expiry policy when creating near cache?

t; > Regards, > -- > Ilya Kasnacheev > > > чт, 23 мая 2019 г. в 17:53, John Smith : > >> So then I should create my regular cache first... Set the expiry policy >> on that and then create near cache on top of that? >> >> On Thu, 23 May 2019 at 08:48, Ilya Kasnache

Re: Which cache gets expiry policy when creating near cache?

Hello! Yes, I guess so. Regards, -- Ilya Kasnacheev чт, 23 мая 2019 г. в 17:53, John Smith : > So then I should create my regular cache first... Set the expiry policy on > that and then create near cache on top of that? > > On Thu, 23 May 2019 at 08:48, Ilya Kasnacheev > wr

Re: Which cache gets expiry policy when creating near cache?

So then I should create my regular cache first... Set the expiry policy on that and then create near cache on top of that? On Thu, 23 May 2019 at 08:48, Ilya Kasnacheev wrote: > Hello! > > It will be set on the cache proxy returned by withExpirePolicy() method > (and will be app

Re: Which cache gets expiry policy when creating near cache?

Hello! It will be set on the cache proxy returned by withExpirePolicy() method (and will be applied to near cache, I guess, if this is implemented at all) Regards, -- Ilya Kasnacheev чт, 23 мая 2019 г. в 00:18, John Smith : > Hi, when we use ignite getOrCreateNearCache().withExpirePol

Which cache gets expiry policy when creating near cache?

Hi, when we use ignite getOrCreateNearCache().withExpirePolicy() Will the expire policy be set on the underlying cache or the near cache?

Re: Near cache only on client node

29, 2019 at 5:10 PM Ilya Kasnacheev wrote: > Hello! > > As this error points out, you can't have near cache with same name as > already existing regular cache. > > Regards, > -- > Ilya Kasnacheev > > > пн, 29 апр. 2019 г. в 13:52, Prasad Bhalerao >: >

Re: Near cache only on client node

Hello! As this error points out, you can't have near cache with same name as already existing regular cache. Regards, -- Ilya Kasnacheev пн, 29 апр. 2019 г. в 13:52, Prasad Bhalerao : > Hi, > > I am getting "*Failed to start near cache* exception" while starting nea

Re: Near cache only on client node

Hi, I am getting "*Failed to start near cache* exception" while starting near cache only on client node. Near cache is not configured on server nodes. Cache configuration on server is node is as follows: private CacheConfiguration agCacheCfg() { CacheConfiguration agCach

Re: Near cache only on client node

ion to the Ignite.createNearCache(NearCacheConfiguration) or Ignite.getOrCreateNearCache(NearCacheConfiguration) methods. Use the Ignite.getOrCreateCache(CacheConfiguration, NearCacheConfiguration) method if you need to both start a distributed cache dynamically and create a near cache for it. - Denis O

Near cache only on client node

Hi, Is there any to enable near cache only on client nodes? I am using partitioned cache and using colocation to submit the ignite jobs. But in my code I do few lookups on client node to validate the data. To improve this lookup performance I want to enable near cache. I saw the example on

Re: Near cache synchronization

, -- Ilya Kasnacheev вт, 4 дек. 2018 г. в 11:08, rom_we : > Hello, > I'm exploring ignite as a distributed in memory cache. > The cache configuration contains a dedicated with ignite server nodes > (partitioned) and application bootstrapping as a client with near cache. > >

Near cache synchronization

Hello, I'm exploring ignite as a distributed in memory cache. The cache configuration contains a dedicated with ignite server nodes (partitioned) and application bootstrapping as a client with near cache. I would like to better understand the implications of running ignite near cache

Re: Is near cache persistent ?

Near cache is a local cache for faster access to data on client nodes. Client node is a node, which connects to a cluster, does some work and could be disconnected after that, it doesn't store data permanently, that's server node's responsibility. -- Sent from: http://apache-ign

Re: Is near cache persistent ?

Hi All, Any comments on this question ? https://apacheignite.readme.io/docs/near-caches does not categorically mention about NearCache being used in persistent mode. Though an example with an eviction policy is given and eviction policy is only

Is near cache persistent ?

Hi All, I have a requirement to create a NearCache (a server and a client are started on the same machine). Is it possible to create such a cache with Persistent configuration and also be distributed. Or does a near cache always have to be governed by an eviction policy ? Regards -- Sent from

Re: Apache Ignite - Near Cache consistency

Correct. Strong consistency is guaranteed for atomic caches as well, including near cache entries. Denis пн, 5 нояб. 2018 г. в 11:21, ales : > Thanks Denis for the answer. > > Actually i am using "ATOMIC" atomicity mode (ie no transaction). > I have been told that it may b

Re: Apache Ignite - Near Cache consistency

Thanks Denis for the answer. Actually i am using "ATOMIC" atomicity mode (ie no transaction). I have been told that it may be linked to the backup synchronicity mode (FULL_SYNC would ensure consistency between nodes and eliminate stale data). -- Sent from: http://apache-ignite-users.70518.x6.na

Re: Apache Ignite - Near Cache consistency

Arnaud, There is a short note on the following page about near cache consistency: https://apacheignite.readme.io/docs/near-caches Here is its text: > Near caches are fully transactional and get updated or invalidated automatically whenever the data changes on the servers. Near cache entries t

Apache Ignite - Near Cache consistency

Hello, I am evaluating Apache Ignite to check if it fits our company's need. So far so good. Now i am trying to understand how the near cache feature works in terms of consistency. We currently have several micro-services with one Ignite configured in client mode in each. All these inst

Re: tuning near cache performance

Thanks Roman, those are interesting suggestions I will try out. Thanks, Scott > On Feb 22, 2018, at 2:10 AM, Roman Guseinov wrote: > > Hi Scott, > > NearCache works fast, except the first get request (NearCache pulls data > from Cache). Avoid entity eviction by setting NearStartSize > size of

Re: tuning near cache performance

Hi Scott, NearCache works fast, except the first get request (NearCache pulls data from Cache). Avoid entity eviction by setting NearStartSize > size of the cache. If this performance is not enough for you, try to make your own HashMap on the client side: 1. Init local HashMap after client node i

Re: tuning near cache performance

Hi Roman, 1. Cache Configuration NearCacheConfiguration nearCfg = new NearCacheConfiguration<>(); LruEvictionPolicy lruEvictionPolicy = new LruEvictionPolicy<>(5); nearCfg.setNearEvictionPolicy(lruEvictionPolicy); nearCfg.setNearStartSize(5); CacheCo

Re: tuning near cache performance

Hi Scott, Performance won't be better than using a local HashMap because there is a lot of additional procedures for replicating, marshaling and so on. In some cases, performance can be improved. Could you provide a more detailed information? 1. Cache configuration 2. How many entries in the cac

tuning near cache performance

would become ignite clients. Currently the idea is to use an Ignite cluster cache / near cache then we'd throw away the custom cross node synchronization logic. The Cache is very read heavy with a small volume of writes over time. When I switched over the mechanism to Ignite I found tha

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

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

Hi there, I have an issue with near cache. I deploy an ignite cluster on server side and run a ignite client in my local. I would like to use NearCache for my local client. Lets say, I have 4 Near cache configuration which corresponding to 4 cache "CacheA", "CacheB", "

Re: Near Cache Topoolgy change causes NearCache to always miss.

Hi Tim, I was able to reproduce the issue. I've created the following jira ticket in order to track this: https://issues.apache.org/jira/browse/IGNITE-6767 Thanks, S. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Client Near Cache Configuration Lost after Cluster Node Removed

I believe i had the same issue, i have posted a test and my finding to the user group. Which can be found here. http://apache-ignite-users.70518.x6.nabble.com/Near-Cache-Topoolgy-change-causes-NearCache-to-always-miss-td17539.html -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Near Cache Topoolgy change causes NearCache to always miss.

Hey Slave, Just some more details, it looks like the GridNearCacheEntry.primaryNode is the suspect. That is what updates the topVer. If you create 2 nodes, then X clients. Using one of the clients to create a cache with a near cache config it seems to work as expected. However, if you create a

Re: Client Near Cache Configuration Lost after Cluster Node Removed

To answer your question, using Visor, one can see cache misses increase upon the scenario described. Furthermore, measure cache.get() calls increase from sub millisecond to 20 to 30 miillis. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

  1   2   >