Hi Andrew,
Thank you for the response.
1. yes, I will try this way to build sub caches
2. yes, make sense.
3. I tested EvictionPolicy, it seemed to be not available in ignite 2.0+,
please refer to my earlier discuss (with denis)
Hi Val,
Here's the background:
I'm thinking about creating message pipelines right in ignite cluster.
it's a nightmare to save data in a centralized cache and run everything on
it,
so my whole idea is to guarantee *none-blocking process* and scalable
consumers.
1. (producer) put real-time
Hi,
1. NodeFilter can be used [1] to bound cache to certain data nodes.
2. You can subscribe to cache updates via ContinuousQuery [2].
But keep in mind, ContinuousQuery listener is called from sensitive code
and it is usually bad idea to make blocking operations in it.
3. To keep only TOP N
Hi Val,
1M per day in memory sales data, 100 parallel financial aggregations in each
batch plus additional PUB/SUB requests for both instant query and server
push. It has been confirmed to play group count distinct is way too slow, so
we decided to play some of TOP N query in separate domain, for
Can you clarify what you mean by "real-time query" in this case? Why not just
start node C as a client and run a query from it?
-Val
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
assume we a ignite cluster of nodes A,B,C, is it possible to create partion
cache only on node A and node B, and use topic message to replicate data to
node C for real-time query? if not, is it possible to create 2 independant
clusters, cluster1 for node A+node B, cluster2 for node C, and let
