Moreover, even if I use custom Affinity what will happen if a node fails (or
a node is added)? Will I be aware / have control at which node its cache is
transferred so I send there co-located jobs?
P.S: this table (SimulationInitialValues) is mainly read-only with the
exception that new entries are added periodically after some ETL procedure
which at some point will stop. The maximum number of rows will be around 5-6
million. Under these circumstances, I am thinking that maybe REPLICATED is a
good fit as well. Most likely we will have 4 nodes.
Also, for a query like the following: select from SimulationInitialValues
where categoryId in (1, 2, 3, 4) and geoChannelId in (5, 8, 12, 14 ,15) and
type =? and week between ? and ?, and forcing local query mode only: what
kind of performance should I expect in terms of milliseconds?
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Distributed-Closures-VS-Executor-Service-tp11192p11863.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
