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 and load 10 entries using client A, then disconnect client A Observe loaded data, with 0 on-heap entries and no clients connected Connect client B with a near cache and get 2 records, populating the near cache with 2 records. Observe 4 on heap entries while Client B is connected. Observe Client B has 2 records in its near cache. Disconnect client B, Observe 2 on heap entries and no clients connected Why do we have some on-heap entries? 2. What is the best way to ensure the near cache is kept completely in-sync with the server cache, would it be sufficient to use a continuous query that makes a cache.get() call whenever the continuous query gets a CREATED event? The cache will keep a small enough amount of data that we do not have a need for an eviction policy. 3. What is the best way to keep a continuous query open indefinitely? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Possible to change cache config without destroying and recreating cache?
Hi All, I have an ignite cache that is getting an affinity backup filter function added (https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/cache/affinity/rendezvous/ClusterNodeAttributeAffinityBackupFilter.html) to it, and I'm noticing that it isn't working unless it is a newly created cache. Is it possible to change/add this filter function to caches that are already created and contain data, or do they have to be destroyed and recreated? Thanks! -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
2.7.0 -> 2.8.1 Upgrade warnings and issues
Hello all, I'm trying to upgrade an existing cluster from 2.7.0 to 2.8.1, and am following the upgrade procedure outlined in the Ignite documentation. I'm noticing new warnings I haven't seen before from my 2.8.1 clients, and am not sure how to get rid of them, or how important they are to fix. *Rebalance batches prefetch count mismatch [cacheName=ignite-sys-cache, localRebalanceBatchesPrefetchCount=3, remoteRebalanceBatchesPrefetchCount=2, rmtNodeId=xxx-xxx-xxx-xxx]* The Rebalance batches prefetch one seems to be an issue between the 2.7.0 default being 2, and the 2.8.1 default being 3, however after upgrading the cluster it is not using the new default of 3. I've tried restarting the cluster, as well as explicitly setting rebalanceBatchesPrefetchCount to 3 in the config, but it still stays at 2. Is this a bug or is there a specific way to change this config value? *Ignite work directory is not provided, automatically resolved to: /app/ignite/work Serialization of Java objects in H2 was enabled.* I'm assuming these other two are less important, but I'm still not sure how to get rid of them. Thanks! -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
