My concern and my requirements are that the cache must be shared with other
jobs or any other application.
If a user or job changes the value in ignite, it must be updated in every
flink job it uses that cache.
Thanks
--
View this message in context:
http://apache-flink-user-mailing-list-archi
I had a DB look up to do and used com.google.common.cache.Cache with a 10 sec
timeout:
private static Cache locationCache =
CacheBuilder.newBuilder().maximumSize(1000).expireAfterAccess(10,
TimeUnit.SECONDS).build();
Seemed to help a lot with throughput….
Steve
On Apr 3, 2017, at 10:55 AM,
Just to add a scenario.
My current arquitecture is the following:
I've deployed 4 ignite node in yarn and 5 task managers with 2G and 2 slots
each.
As cache on ignite I have on record in key/value (string, object[])
My thoughput without ignite is 30k/sec when I add the lookup i get 3k/sec
My ques
