Re: Secondary Key for ignite cache?

We can cache it as the full object, but that means we have to use the processing power to marshal and unmarshal the object again, which is part of what we're using the cache to avoid. We've seen significant CPU usage improvements using this cache system so far against production simulated

Re: Secondary Key for ignite cache?

The object we're mapping to in the cache isn't the complete object - it's basically the tostring of an object after it's been formatted for the user. So if you had an object called foo with fields id, bar1, bar2, and bar3, and the user requested that object with just the id and bar2 field, in

Re: Secondary Key for ignite cache?

The cache maps from a key that contains (the object id, the fields being returned, json/atom/rss format) and maps it to the formatted string for that object in the specified format. So when we're searching the cache for the object, we're querying using all the formatting information, but we want

Secondary Key for ignite cache?

Is there a way to set and use a secondary key in ignite cache? Our use case is that we cache string representations of objects using a complex key that provides additional information about formatting, but we want to invalidate using just the object ID. There are many combinations of formatting

Re: Cache hit rate for Ignite not adding up

And another: After restarting a node, the local stats show that it has 162K cache puts, but only a size of 81K. It's not quite double, but it's really close. Does that mean there's 81K duplicate puts that were ignored? Or does it mean something else? -- View this message in context:

Re: Cache hit rate for Ignite not adding up

Another example of this not really adding up: I run a test hitting a bunch of data. We get a low cache hit rate, as expected, but presumably we're filling the cache with everything we missed. Nothing is getting removed from the cache, according to the metrics through jconsole. So then I run the

Re: Cache hit rate for Ignite not adding up

Shouldn't Ignite be putting an object into cache every time it's missed, though? As long as it isn't running out of room, shouldn't it have one entry for every time it missed? Another question I have is: when it says there are X misses, does that mean: 1) X times, this host looked for an object

Cache hit rate for Ignite not adding up

I've got a process running ignite with 5 nodes, and a partitioned cache. Checking jconsole for the hit rates and stuff, I see the following: CacheGets: 912287 CacheHits: 142473 CacheMisses: 769814 Size: 27539 CacheRemovals: 0 CacheEvictions: 0 The other hosts have very similar stats. The

Re: Performance issues with Ignite L2 cache compared to ehcache

Let's see... 1) we've got 5 hosts running the service, each of which has an ignite instance. 2) we currently don't have any ignite-only nodes, just the ones embedded in the service. 3) spring-ignitecache.xml 4)

Performance issues with Ignite L2 cache compared to ehcache

So I've got the L2 ignite cache working, confirmed with beans, logging, etc, and we're comparing it to our existing ehcache implementation. Unfortunately, so far it seems to be running far fewer operations per second than the ehcache version. However, it does seem like the timing on each cache

Re: Configuring ignite distributed hibernate cache

Excellent, that did the trick! Thanks a lot for the help. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Configuring-ignite-distributed-hibernate-cache-tp7975p7982.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Configuring ignite distributed hibernate cache

I'm using the hibernate caching ignite provides (as documented here: https://apacheignite.readme.io/docs/hibernate-l2-cache) and having some difficulty getting the caching to work in a distributed manner. It works fine when the object is cached locally, and it seems to be aware of the other

Re: Logging failing, tried the troubleshoot steps already

I thought the purpose of using log4j was to avoid the steps in that link? The link I included says "you can either add ignite-log4j module to the list of the used jars so that Ignite would use Log4j as a logging subsystem, or alter default Spark classpath as described here." Does "adding it to

Logging failing, tried the troubleshoot steps already

I'm trying to implement caching using ignite, and when I start it up (Ignition.start) it throws an error: Can't load log handler "org.apache.ignite.logger.java.JavaLoggerFileHandler" java.lang.ClassNotFoundException: org.apache.ignite.logger.java.JavaLoggerFileHandler