As an administrator, I want to change the max-entries value for eviction for a clustered cache without requiring a server restart. Ideally, I want to perform this operation once for the entire clustered cache (not one-by-one for each node).
Is it planned to do some changes in JDG JON plugins with regards to these changes? Does it somehow affect working with JON web console? (Adding new feature, work-flow etc.?) Thanks!
Rejecting this feature for now, because JON needs to be modified to allow users to change the MaxEntries value for a cache. I will work on testing the functionality using JConsole and the API.
Good news. I've tested library plugin with JDG 6.4 DR4 invm application and it exposes desired operation: [cache] Sets Max Entries for eviction. I was able to reconfigure the value and it works. When adding entries, number of current cache entries never goes beyond specified value. OK I've met a small issue when I tried to set max entries threshold for a cache where it is NOT configured eviction from the start. For instance: ConfigurationBuilder configFCSdist = new ConfigurationBuilder(); configFCSdist.jmxStatistics().enable(); configFCSdist.persistence().passivation(true).addSingleFileStore().location("/tmp/"); configFCSdist.clustering().cacheMode(CacheMode.DIST_ASYNC).l1().enable(); Then I am getting this exception via JON UI: Caused by: java.lang.UnsupportedOperationException: Resizing is supported only with eviction at org.infinispan.container.DefaultDataContainer.setMaxEntries(DefaultDataContainer.java:281) full stack trace: http://pastebin.test.redhat.com/321065 That makes sense, of course, but don't we want to allow set eviction also for caches that does not have evicition in their configuration YET? Also, server plugin does not expose the operation YET and should be fixed in next release. @Afield I believe we can postpone verification until server plugin is delivered with the added feature (operation for configuring max entries parameter). Note that we might experience the same issue when trying to "reconfigure" server cache that does not have evicition configured. Thanks!
Yes, that is correct. Setting max entries is strictly connected to the eviction (without it, this feature does not makes sense). Allowing users to set this value without eviction might be misleading (they might expect that max entries will magically work as they expected, but technically we would be waiting till the user configures eviction). I would vote for leaving it as is.
Thanks Sebastian! That makes perfect sense to me. Just wanted to be sure and also hear your oppinion. Alan said he is tracking new operation for server plugin in another BZ. Then, my status for InVM JON plugin is that this feature works as expected. @Alan, if this feature is OK from functional perspective and tests are passing, you can set it to verified, then. Thank you all for the info :)
Verified with JDG 6.6 DR4 with InVM JON plugin. Server JON pluging tracking BZ is https://bugzilla.redhat.com/show_bug.cgi?id=1272490 I agree that changing the eviction configuration is probably not the correct thing to do at this point. It would be even better if this operation were not available when eviction was disabled, but hopefully that can be achieved in the new Management Console. Thanks for your help, Tom!
This product has been discontinued or is no longer tracked in Red Hat Bugzilla.