Hi 2) Also you can subscribe to local node events and update other caches when event is received on primary node for key to avoid excessive calls.
On Wed, Apr 12, 2017 at 7:35 PM, Andrey Mashenkov < [email protected]> wrote: > Hi, > > 3) Initial query is not mandatory, you can set it to null to receive > updates only. > > Also, you can try CacheInterceptor to update other caches synchronously. > It can cause performance issues as > CacheInterceptor methods are called from sensitive part of code inside > synchronized block, but it should be ok, > if you update same key in another cache and it is one-way cache > synchronization (so, deadlock is not possible). > > > On Wed, Apr 12, 2017 at 7:18 PM, nskovpin <[email protected]> wrote: > >> Hello, Ignite team! >> Assume that i have a big cache A (key - id, value - date, etc ). This >> cache >> is being updated every 5 minutes. My question is: what is the best way to >> update my other caches, that were built from cache A (value has a field >> "date"). I have some thoughts: >> 1) I can create broadcast or computeTask, than read A's local entries and >> update another caches (but i should read all my entries, even they haven't >> updated yet) >> 2) I can create cacheEvents and update another caches - but i've read that >> events are designed more for auditing purposes. >> 3) I can create continuous query, but i don't need to query my data:) >> >> >> >> -- >> View this message in context: http://apache-ignite-users.705 >> 18.x6.nabble.com/Repeatable-cache-updates-tp11910.html >> Sent from the Apache Ignite Users mailing list archive at Nabble.com. >> > > > > -- > Best regards, > Andrey V. Mashenkov > -- Best regards, Andrey V. Mashenkov
